question

Can you please raise a ContactUs ( https://developer.amazon.com/help/contactus.html) with logging in from your account. We will reply with Certificate hash key details.

We have a similar problem. Our app is rejected by the Amazon Submission test because post to to Facebook fails. We have already contacted amazon support, they have sent us the key hash. We added the hash to the FB developer app, resubmitted the app to Amazon and again the post is not working. If I test this feature with my own APK (signed with my keystore) it works fine. On the FB app page I have added both hashes my own and the one sent from Amazon. I would also like to point out that the same app is live on Google Play and working without a problem. I have also found out that my new app didn't have a security profile assigned to it. I've created one, written to amazon support, to send me the new hash for facebook. I got no reply. Any ideas how to solve this?

Hello ZomboDroid, In order to investigate this issue further we will specific information about which app in your account is causing this problem. To protect the personal information of developers, we do not discuss the details of specific applications on these discussion forums. Please reach out to us via our Contact Us form ( https://developer.amazon.com/help/contactus.html ). This will allow us to validate your identity and discuss app specific information in a context that will not expose your personal and proprietary information.

Hello If you are using the Facebook SDK so your user can post directly a message from your app, then be sure in the FB API call to set your application name in the ShareDialogBuilder if this is the class you are using. Aka: dialogBuilder.setApplicationName("xxxxxxxxx"); Just like you my app was not able to post when running on Fire OS but was running fine if published on Google Play Store. After adding the proper API call when building the dialog, then the app started to work and was accepted in the Amazon App Store Looks to me like there is either a bug in the Facebook SDK on Fire OS or simply a bug in Fire OS... Hopefully that will help solve your issue.