-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDK Registration failed #198
Comments
i still got the issue but i want to inform you that i have checked both API keys and they are both created and registered correctly. So the problem i am facing right now is that i don;t get the registration failed message, i only get the ''registering please wait..'' and when i connect the phone with the controller the app does nothing. the only button i am able to press is TEST MODE. |
If your API key is correctly placed in the AndroidManifest file, package name is correct, and you have internet access on the phone it should connect (did for me). Did you also fill the Google maps API key? For connecting to the drone, yes you just connect the controller to the phone with USB cable and the controller to the drone as usual. |
they are all correct but nothing is working :( . Can i get the apk from someone who has already has created the app ? |
I have a same issue. Did you find out a solution for it? |
I think, dji sdk is not supported in your region, because when i changed my region with vpn to france and created new account with new key, Rosetta started to work. However now i have problem with connection to qgs. |
Describe the bug
After i generate the APK file from android studio
and after installing the app on my android device i get this messages
the package name in the dji developers sdk key is correct (sq.rogue.rosettadrone)
And can someone tell me which steps should i take to connect my android device to my dji air 2s when i fix this registration problem?
Steps To Reproduce
No response
Screenshots
No response
Drone Model
Smartphone Model
Additional context
No response
The text was updated successfully, but these errors were encountered: