I'm trying to change my Dropbox application permission from 'App folder' to 'Full Dropbox'. By application I mean 'My apps':
I'm doing this to access all the functions provided by Dropbox API, otherwise an error is shown, for example:
Error in call to API function "sharing/get_folder_metadata": Your API app is an "App Folder" app. It is not allowed to access this API function.
Anyway, I've read that the only way to change the permission to an app is by creating a new one. Therefore, what I did was, created a new app with permission type 'Full dropbox' but for some reason it didn't even show up under 'Dropbox > Apps' directory.
According to developers guide if app has permission App folder then it is moved under Apps folder automatically. I tried also that but the folder didn't appear there for some reason. So, why the first application is showing..
Can there be only one active app, like, should I download all the data from first one, delete it and then create new app with Full permissions?
It's not possible to switch the permission on an existing Dropbox API app.
If you want to change the permission used for an app that hasn't been released to users, you can do so by deleting the current API app registration and registering another with the desired permission. Deleting an API app in development mode frees up the name so you can register it again. Once you do, just be sure to update your app accordingly to use the new app key and secret. Access tokens for the deleted app will also no longer work.
If your app has already been released to users, we do not recommend disabling your API app, as it would break the integration for existing users. Instead, we recommend you register another API app for the other permission and add that as an option in your app.
You can register a new API app here:
https://www.dropbox.com/developers/apps/create
There isn't a limit on the number of API apps that can be owned by or linked to a particular account.
Your second App Console screenshot shows that you do own two API apps: one with the "app folder" permission, and one with the "full Dropbox" permission.
Note that only apps with the "app folder" permission get a special "app folder" automatically created under "/Apps". Apps the with "full Dropbox" permission do not, and instead can access any path in the account.
Related
I would very much like to enable users of my app to backup some of app data on their own Dropbox. I would like to direct users to login to their Dropbox account with their email and password and then the app would generate and store a file there without users having do anything on their own.
Is this possible?
I wouldn't want users to have to go to Dropbox App Console and then Create App and then fill in all the options and then copy the access token and paste in my app manually. That would repel a lot them.
I haven't seen anything in the docs suggesting that programmatic access to an account without an app created in the Console and generated access token is possible? Did I miss something?
Yes, this is possible. You as the developer would register the app once, and implement the Dropbox OAuth app authorization flow in your app to allow your end-users to then connect your app to their accounts.
You may want to check out the following guides:
https://www.dropbox.com/developers/reference/getting-started
https://developers.dropbox.com/oauth-guide
https://developers.dropbox.com/dbx-file-access-guide
I have a terrible question..
I hope there is anyone who know this problem..
In EXPO App which is a wrapper API for React Native,
How can Expo Image picker example app can access Gallery(external storage) without requesting any external storage access permission to user???
original source code is here..
https://docs.expo.io/versions/latest/sdk/imagepicker/
I tried with removing any askAsync(CAMERA_ROLL.permission) or getAsync(CAMERA_ROLL.permission).
So the example app has no permission about accessing external storage...
BUT!! I press the button, It access the Gallery....
How can it be possible??
I double check permission on the app, but there is no granted permission to external storage...
Please let me know...
I think it is the appropriate thing which firstly asked permission, then access the external storage..
P.S I tested it with android phone only.
i have never checked permissions..
To stop expo app from having this permission, do the following:
Remove all reference to the permission requests (That you already did)
Remove the Image launcher (but it seems you don't want to do that)
Clear the expo application permission of media access
Step 3 is what you are looking for, to clear application settings go to your phones settings -> application management -> select expo app -> permissions and clear the gallery/media permission.
Now when you run the application again you will not be able to access the gallery even if you press the button as you mentioned and if you include the getAsync to request for permission you will be prompt with asking for permission.
EDIT:
To explicitly set permissions for stand alone applications modify your app.json file and add the "permissions" parameter under the android configurations there, by default expo uses all permissions of your device. specify there the permissions you want your application to have.
Please refer to this link for further details on how to configure your app.json file.
Hope this helps!
We are working in RingCentral application and APIs with SMS and fax permissions.
The application recently moved to production from Sandbox environment.
We have now a requirement to add 2 additional permission ReadAccount, ReadContact in the app which was not added during sandbox testing.
How can we do that? I don't see any option to modify the app. Is there any way we can modify the existing app?
As per I know once your app is in production, you cannot change anything.
You need to ask devsupport#ringcentral.com for any help. Once they added the permission with your request (not sure if they do.. most probably they don't) you need to test again for that permission you acquired.
The official recommendation is to create a new app, add proper permissions and graduate it. So in that case you need to go through again.
As per the reference here
"You can clone the app, give it a new name or add a version to the new app name. Add the missing permissions and run test in the sandbox the same way as you did for the first app. Graduate your app and finally replace the client Id and secrete to use the new app. You can suspend the old app after that."
Similar question here: https://forums.developers.ringcentral.com/questions/1059/how-to-add-permissions-of-read-call-log-in-product.html
I am trying to add a new account and allow that account to access the Bigcommerce App Store.
I followed the tutorial on Tutorial
I have created the account, assign all the permissions by setting the user role to Store administrator as shown below. Somehow, the user I have created still can't access Bigcommerce App Store.
Could someone please tell me what I am missing? Thanks
Only store owners have access to the single click apps on the Bigcommerce Appstore at this point. This is both to install and access the app once installed.
You can find documentation on that here: https://support.bigcommerce.com/articles/Public/How-do-I-access-and-install-the-new-single-click-apps-within-my-Bigcommerce-store-control-panel
------- UPDATE -------
As Alyss correctly indicates, BigCommerce has now updated the app system. Now, if an app is setup to handle multiple users, it is possible for users other than store owners to access an app.
When debugging a GDAA app, I need to re-test a "brand new account" situation. I.e. getting the dialog that asks user to allow the Drive access:
"[YourApp] would like to: View and manage Google drive files that you
have opened or created by this app"
Is there a re-set method that would get me back to ground zero?
You can reset this via the Drive "manage apps" page on the web. Disconnect the app from your drive.
Have a look at the 'Google Settings' app on your device, in the 'Connected apps' section you should be able to select and disconnect your app. At least for other kinds of permissions (e.g. contacts), allowed apps show up there.
Edit: The same can be done via the web here.