app secret and and app key no longer working?

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.)

The error I get is this:

[WARNING] DropboxSDK: error making request to /1/account/info - (400) invalid_request

i double checked the values against my app page and even reverted to older versions of my code where the app was definitely working.

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:

[self.restClient loadAccountInfo]

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:

https://www.dropbox.com/developers/contact

Thanks in advance! 

OK, but how do I upload the project?

Also, if I can reproduce the error by a REST request, I guess I can send you the REST query.

Feel free to use a shared link to share the project.

If you can reproduce the error with a manual request, e.g., using curl or something, that would be fine too.

Ok done. The app secret is included in the API ticket, but there is no other way for you to test it. 

Thanks! We'll look into it and follow up with you in your ticket.