I’m having the same issue where it says cannot find app using Client App ID
i created another app to check and replace that id still same issue.
I also used url authentication https://realm.mongodb.com/api/client/v2.0/app/<my-app-id>/auth/providers/local-userpass/login.
but still the same result.
It looks like this is not fixed yet, right? I just created an App and enabled the Data API … but, am getting the same exact error when trying a sample POST from postman
{
“error”: “cannot find app using Client App ID ‘the-app-id-here’”
}
So … disabling drafts under Deployment->Configuration solves the problem … kind of. Certain clients can connect while others continue to get the error …
Also, possibly having App Settings → Deployment Region global works better than local (though, I am not sure that you can make this change after the app is created). Glad this is all “GA” …
It looks like there are a ton of views on this issue and it looks like it has been out there for a while. Is there anyone looking into this issue? Is there a bug number that we could follow to track any progress?
Also, it would be nice to understand how Mongo reviews these communities and why something like this might sit for this long, without any comments. Am I just missing them?
I appreciate you raising your concerns and apologies for the delay. The replies to an old topic are sometimes not visible in the queue.
There is not a single reason for this error to happen. Deployment Region, internal SDK URI mapping, etc could be some possible reasons. Unfortunately, on June 02, 2022, during our regular release cycle, a bug got introduced that caused locally deployed apps not to be found. The bug was isolated to a limited number of apps in a subset of regions. This has been fixed since.
@Dima, could you please let me know if this is happening in your prod or dev environment and what is the app name it is happening for?
@Haikun_Huang could you please share the app name where this is happening? Your app logs are not showing the error. Could you confirm if this is fixed for you?
Thank you for your reply and appreciate your feedback. It’s always helpful to know areas where we can improve.
Could you please share the time period when this was happening? What SDK are you using? What local region was your app deployed and what is the cluster location? There may not have been a need to change the deployment model but glad to know this was resolved for you.
The SDK issues are available to search on Github based on the language stack you are using but the cloud issues are internal unless there is an outage that gets highlighted on the respective status pages.
This was at the time of the reply to the original post, around June 16th, 2022.
No SDK; just postman POST to the Data API endpoint.
The app region initially was the one it defaults to … I believe in our case that is AWS us-east-1 (same as the cluster location)
As far as not needing to change the deployment model, I disagree. It simply did not work (as per the post) when the deployment region was local instead of global.
It would be great to see cloud issues somewhere; this way, if anyone runs into a problem, you can at least see if it is a known issue.
Thank you for your patience and apologies for the delay in getting back to you.
This definitely should be a one-off, perhaps a residual effect of the bug that unfortunately was introduced. Could you try again with a test application with local deployment?
Your feedback is definitely noted, but since this was an internal issue and was fixed rather immediately, this was not highlighted.
Please let us know if you would have any more questions or if it is fine to close this topic.