Hi, Currently, the
api_key.txt is stored in the assets folder, but what if my other API also requires me to have a file called
api_key.txt in the same assets folder. This could potentially lead to conflict. It would be better if the
api_key.txt is stored with it proper path such as "assets/amazon-device-messaging/
api_key.txt", instead of "assets/
api_key.txt" How does ADM plan to fix this issue and when can we expect the changes to be in the ADM API? This is high-priority, please address soon. Thanks,
Hi Adm_ms, Thank you for posting. Can you be be little specific what did you mean by "other API"? The conflict is already reported for using "Log in with Amazon" and ADM (or GameCircle 2.0) in this thread :
https://forums.developer.amazon.com/forums/thread.jspa?threadID=1293&tstart=0 We have raised the issue to the right team. Please let us know if you have any concern other than this. I will notify you all in this thread after getting update from our team. Thanks.
Yes I have a network API key that's not related to ADM or "Log in with Amazon", but it also needs to be call
api_key.txt and stored in the assets folder. This causes a confusion for both ADM and my network API.
Hi Adm_ms, We need one input from you to investigate the problem you reported. Are signing the app on your own? Which certificate your are using to sign the app? Is that debug or a custom cert made by you?
Hi Adm_ms, Are you using "Login with Amazon" and GameCircle/ADM in production? I guess not because I think you are unable to proceed due the issue. right? The issue would be fixed from our side but this would take time. So I can not commit any date on that. We can manually fix the problem if you can provide the app/vendor details. I have seen only two test apps are associated with the account you have used to post on this thread. I think this account you do not use for production apps. Are your apps what uses "Login with Amazon" and GameCircle/ADM already in production? If not, can you write a ContactUs(
https://developer.amazon.com/help/contactus.html) from the account you use for production so that we can track your vendor information and apply the fix from back end? If your apps are not live, can you create the app, security profile you will be using in that app and send us the details through ContactUs (since your account information should not exposed in the public forum). Please mention this thread url in the ContactUs (
https://forums.developer.amazon.com/forums/thread.jspa?threadID=1298&tstart=0) you are going to raise.
Hi Adm_ms, The fix for API would take time to be live. But in the mean time we can manually fix the problem from back end case by case. And that is why we want you to raise a ContactUs from the account you would be using to publish the app what will have LWA and GC/ADM integrated. So that we can manually fix the problem from back end to enable to use same api key for both sdks. Hope it makes sense.
Hi Adm_ms, We did not hear from you. The problem reported in below thread regarding the same issue has been fixed from back end in the way I mentioned above.
https://forums.developer.amazon.com/forums/thread.jspa?threadID=1293 In order to get the fix in your app, please send us the app and security profile details through ContactUs. Thanks.