question

jtpdev avatar image
jtpdev asked

App issue: lack of good info in Amazon's email

Amazon it will be great if you were to attach some logcat when reporting that a feature doesn't work as expected. I already did use the contact us link provided to ask for more information including logcat and after updating my code just in case to catch some errors and resubmitting I am getting from Amazon the same report. Sadly I tried my app on many devices and different scenarios and they all work. So without being able to see a logcat I am afraid it will be difficult to fix. For everyone else: Amazon is reporting that when I use the Facebook SDK api and the FB Share Dialog Builder the share screen appear and disappear right away. Anyone experienced that? I try to reproduce many times but zero luck so far and without a logcat or stack it is going to be difficult to diagnose. Does anyone know if Amazon test really on all devices or rather use a bunch of Virtual Machine running Android?
fire tabletsubmission testing distribution
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

jtpdev avatar image
jtpdev answered
Replying to myself: clearly the issue seems to be on the Amazon side. I did release the same app (Signed) on the Google Play Store yesterday and the app is working without problem... So it seems the issue that Amazon is experiencing is really related to the way Amazon does their testing. Unfortunately not having any log cat is not helping diagnose the issue.
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Sujoy@Amazon avatar image
Sujoy@Amazon answered
We apologize for the inconvenience. This issue happens in all the Kindle devices and non Amazon devices and below is the exception that is caught by Facebook SDK. This is causing incorrect functionality while trying to share a movie in FB in your app. 09-04 16:41:43.852 807-830/? I/ActivityManager﹕ Displayed com.facebook.katana/.activity.composer.ComposerActivity: +444ms 09-04 16:41:43.852 20896-20896/? W/IInputConnectionWrapper﹕ showStatusIcon on inactive InputConnection 09-04 16:41:43.882 20896-20896/? W/FlurryAgent﹕ End session with context: com.jetap.android.moviepreview.ui.MovieDetailActivity@4346a9d0 count:0 09-04 16:41:43.902 807-832/? V/DoNotDisturb﹕ Top component: com.facebook.katana/com.facebook.katana.activity.composer.ComposerActivity 09-04 16:41:44.052 14031-21319/? W/fb4a(: ):BlueServiceQueue﹕ Exception during service com.facebook.http.protocol.ApiException: Unsupported get request. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api at com.facebook.http.protocol.ApiResponseChecker.b(ApiResponseChecker.java:103) at com.facebook.http.protocol.ApiResponseChecker.a(ApiResponseChecker.java:136) at com.facebook.http.protocol.ApiResponseChecker.a(ApiResponseChecker.java:219) at com.facebook.http.protocol.ApiResponseChecker.a(ApiResponseChecker.java:184) at com.facebook.http.protocol.JsonResponseHandler.a(JsonResponseHandler.java:37) at com.facebook.http.protocol.ApiResponseHandler.b(ApiResponseHandler.java:78) ... ... ... at com.facebook.http.protocol.AbstractSingleMethodRunner.a(AbstractSingleMethodRunner.java:18) at com.facebook.platform.common.server.SimplePlatformOperation.a(SimplePlatformOperation.java:40) at com.facebook.platform.common.server.PlatformOperationHandler.a(PlatformOperationHandler.java:60) at com.facebook.fbservice.service.BlueServiceQueue.e(BlueServiceQueue.java:329) at com.facebook.fbservice.service.BlueServiceQueue.d(BlueServiceQueue.java:55) at com.facebook.fbservice.service.BlueServiceQueue$3.run(BlueServiceQueue.java:258) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:390) at java.util.concurrent.FutureTask.run(FutureTask.java:234) at com.facebook.common.executors.ListenableScheduledFutureImpl.run(ListenableScheduledFutureImpl.java:59) at android.os.Handler.handleCallback(Handler.java:747) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:151) at android.os.HandlerThread.run(HandlerThread.java:60) Solution: you need to update new hash of the apk that is signed by Amazon's certificate. We are sending the required information through the ContactUs case that you have created for this issue.
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

jtpdev avatar image
jtpdev answered
Sujoy unfortunately nope I do already have the proper key hash in place for the app in the Facebook settings. According to the log file I did received I believe the Facebook app used on the tested device is either an old version or incorrectly setup (aka user not logged in). I just sent a new ticket, and I am seeing tons of Facebook error which seems to indicates the device used for testing is not properly setup. Here is part of the support/contact us info I sent: ==== If you look inside the log file you can see clearly that Facebook is either an old installation or the user is not properly logged in to Facebook on that device. You can see many exceptions generated by Facebook app on the tested device:- line 1362 of the log file:09-08 18:33:39.666: W/fb4a(: ):BlueServiceQueue(11804): com.facebook.http.protocol.ApiException: Error validating access token: Session does not match current stored session. This may be because the user changed the password since the time the session was created or Facebook has changed the session for security reasons. which is followed by a full stack trace showing error inside Facebook - same errors and stack trace at lines: 1476, 1512, 1541, 1576 etc... - line 1931: Facebook app showing error at login: 09-08 18:33:45.826: W/fb4a(: ):FacebookLoginActivity(11804): java.lang.Exception: No access token in reply: Bundle[{error_code=190, error_msg=missing device token}] - line 2001: Facebook app showing some other error, trying to parse data: 09-08 18:34:01.496: W/Bundle(11804): java.lang.ClassCastException: java.util.ArrayList cannot be cast to android.os.Parcelable - line 2118: Facebook app showing other errors with unsupported request: 09-08 18:34:12.176: W/fb4a(: ):BlueServiceQueue(11804): com.facebook.http.protocol.ApiException: Unsupported get request. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api ==== It looks more like issues with the Facebook app and the device rather than my application itself... Can someone properly verify that Facebook latest app is installed and the user is properly logged in. I did verify my app on multiple devices and it's working fine. The same version of the app on the Google Play Store with the same feature is working fine. So this is an issue on how Amazon is doing the test with a device that is not properly setup. It's IMPOSSIBLE for me to check your device is incorrectly setup and the issue is not in my app, thus I can't fix the problem. The app has been now rejected multiple times and I am waisting time and time over due to improper testing. This is really frustrating.
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Bipin@Amazon avatar image
Bipin@Amazon answered
I tested your app using the latest Facebook version available on the Amazon Appstore - Facebook version 8.0.0.26.24 .
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

jtpdev avatar image
jtpdev answered
Hi, and what results did you get? The same binary app submitted to Google Play Store works; running the app on my Kindle Fire HDX 7, and Kindle HD works... Same with my non Fire OS devices (phones & tablets). The logs I got show issues with Facebook app and there is no stack trace from my app code, so it is impossible for me to fix anything on my side... So I am not sure how to proceed from here: it seems that the fastest solution will be to drop the feature on Fire OS platform. Could you send me a new logcat from the last attempt you did?
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Sujoy@Amazon avatar image
Sujoy@Amazon answered
The latest version of your app no longer seem to have issues with Facebook sharing. Can you please confirm the issue is fixed from your side? When you submit to Amazon, your app is signed with a signature generated by Amazon. It is therefore important to update your Facebook app settings with the updated hash key could solve the issue.
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.