while playing with the following initialization function:
initWithAppKey: [Constants dropboxAppKey]
appSecret: [Constants dropboxAppSecret]
for once I supplied the correct appSecret with an invalid appKey to see how it will behave. It gave a 400 error but then when I restored the correct appKey, it no longer worked.
I am sure the problem is not on my side, because I reverted to older code which was working and still could not get past the authentication.
Do you have any security measures that disable the auth on wrong combinations?
Do I have to ask for new credentials ?
If you reverted back to the correct values, there wouldn't be any reason to still receive an error.
Can you share the full error/output that you're currently getting?
I also recommend logging out the values of Constants dropboxAppKey and Constants dropboxAppSecret to make sure they're what you expect. (Don't post your app secret though.)
Can you share the code you're using to check the values? Also, when/where are you checking them? Maybe they're getting altered somewhere along the way. If you can share the output that may be helpful.
Also, please share the rest of the code for the actual API call you're making.
when I say double-check I myself am comparing to the ones that are on the "My apps" page. And they are correct, there is no chance that i give the wrong credentials. I am sure because i get the same error even when replacing the constant variables with literal strings.
the actual method i am calling is the following:
where restClient is an object called like this:
self.restClient = [[DBRestClient alloc] initWithSession:[DBSession sharedSession]];
self.restClient.delegate = self;
That code looks fine, and I haven't been able to reproduce this unfortunately. That being the case, can you share a small sample project that reproduces this so we can look into it?
You can send it via an API ticket if you'd prefer to share it privately:
Thanks in advance!
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!