Have anyone tried to add AndroidMobilePushApp (is provided by AWS) into Eclipse IDE, follow by this tutorial (http://docs.aws.amazon.com/sns/latest/dg/mobile-push-gcm.html) and able to get registrationID for the Amazon Mobile Push app?
I am able to add AndroidMobilePushApp into Eclipse along with 2 extraneous library .jar (android.jar, google-play-service) without any error, created Google API project on Google APIs Console website and copied that project_number into [res/values/strings.xml] according step 3 from the tutorial above. However, when I deploy the application into an Android device (Version 2.3.6 and API level 10), the app does show up,but it doesn't run when I click on...with error says " The application Amazon Mobile Push ( process com.amazonaws.androidtest) has stopped unexpectedly. Please try again! " so It won't able to give me back registration ID as step 4 from the tutorial above.
Any idea why?
Thanks,
Don
I had trouble w/ that sample code also. I finally got AndroidMobilePush to work but not SNSMobilePush in the same tutorial.
Hard to tell what you have done or left out, but I can give you some ideas of where to look:
Check if you have changed package names any place.
I had to declare the PLAY_SERVICES_RESOLUTION_REQUEST = 9000; constant needed in checkPlayServices()
Make sure you have not blocked execution of checkPlayServices and register()
I would set a Log filter to make sure you are at least getting that far. Then, of course, set another to capture the registrationID so you can save it to log.txt. Copy that and supply it to the SNS Console in AWS when you Add Endpoints.
Read carefully Step 3, point 4 and associated image.
If you remove android.jar from the export list, your app will run fine
Related
I'm developing an android app that won't be downloaded via the Google Play store but instead through an APK listed on my website. I was looking for a way to update this app.
I've done some research and I think the best way would be to run an API at the start of the app that checks the downloaded app's version against the version of the APK listed on the website (at the time of app launch). If the version of the website APK is higher, then I prompt the user for an update. Ideally the API would get the APK itself without the user needing to go to the website.
I have some doubts about this that I hope someone can answer however:
First - Once I download the new APK does the old one get deleted or do I have to do that?
Second - How do I keep User Preferences?
If this isn't the right way to do it I'd appreciate any tips.
If it is the right way and you know of some good resources to build an API like this I'd appreciate those too!
I have been developing a simple game for android and I have run into a number of issues while using in app billing. To perform IAB, I use the utility classes provided in the TrivialDriveExample here. I have copied and modified accordingly the code in the MainActivity class provided in this example to use IAB. I have also followed the documents on the android developer page describing how to set up IAB on the developer console.
However, when trying to test the purchase the product in the app using the following code, I get the error described in the title of the question.
helper.launchPurchaseFlow(game.getActivity(), sku, RC_REQUEST, getPurchaseListener(game));
(where helper is an instance of the IabHelper class provided in the google code link above and RC_REQUEST is a constant set to 10001 as shown in the MainActivity in the trivial drive example, and where sku is the sku of the product - as seen in the developer console). Here, getPurchaseListener returns an instance of an IabHelper.OnIabPurchaseFinishedListener (provided in the util package of the example code).
What I am certain of:
The sku is correct and exactly the same as the one provided on the developer console.
The APK that has been uploaded to the developer console as alpha is identical to the one installed on the device (and is signed with my developer key not the debug key).
My account and all used testing accounts are in both the google group registered for alpha testing and the list of accounts that receive the LICENSED response from the developer console.
Every object used in the code != null
I can test Google Play game services on my app (achievements & leaderboards).
It is to do with the app I am developing as IAB works for other apps (tested with Clash of Clans and Infectanator).
What I have tried:
Removing my developer google account from my device, leaving only a test account (+waiting overnight without my developer account installed on my device and then testing it in the morning with my test account).
Clearing all google play data and caches.
Restarting my device/reinstalling the application.
I also get another error when trying to use android's test purchases (using the sku 'android.test.purchase'). I get this:
Error while retrieving information from server [DF-DFERH-01]
As mention above, I have cleared google play data, removed my account and added it again, restarted my device and reinstalled the app. Again, this happens only on my app currently in development and not in any other apps with IAB.
EDIT
Just to note, I have looked through other people's questions regarding this error and tried the solutions provided to no avail.
The application with IAB integrated has to be Published for Play Store to enable the billing for it, it won't work so long as it's in Draft -- documentation seems to not be very clear about this.
So, make sure you actually publish the app (don't worry, if you've only got the alpha and/or beta version, it won't be listed in Play Store for simple mortals) and, as usual, allow some time for Play Store to absorb it.
Same answer here
I am trying to implement the APK Expansion Downloader Library into my application, but I am struggling to get past the LVL verification check.
Everytime I run up the application, I get a "Signature verification failed" message back from the LicenseValidator class. The application is signed in release mode, with a proper Keystore.
I have checked maybe 10+ times that the PUBLIC_KEY I am using inside of the application is the same as on the developer account, yet its still not working. I have also uploaded the application to the Play Store, with the expansion file (correctly named), and even added in my account as a Test account on the developer console. I have also tried adding the publisher account onto my device, and its still not working.
I do not know what to do next, I need this to work and cannot find any help on the internet as to how to fix this.
Thanks
Adam
you had several versions of file extansion? Because I had the same problem as the api sent me the name of an old file ... as a workaround in the verification code I just replaces the version number ... It's not terrible, but the bug does not come from me ...
Fixed. Via "Manage apps" I stopped the Google Play Store app, cleared its data (not the cache, which was zero bytes), then restarted my licensed app - licensing now works.
The problem I'm trying to solve- I'm trying to get deep linking working, and testing it with Emulator. When clicking on posts, the links direct to the mobile web site. This is in the case of the user having permissions for the app, and the app is installed (on the emulator). In the Facebook app, it even acknowledges its out of date, but an upgrade (in app) crashes.
I also noticed that the Facebook app installed on the emulator is out of date (I installed it via adb install facebook.apk from github sdk).
SSO is working fine, and I have setup deeplinking effectively with iOS before (So I know how ti's supposed to work/test it, etc.). But the port to Android is being held back by this out of date 3rd party Facebook app. I'm assuming testing on device will solve it, because there the Facebook app will be the latest (which brings to mind- what if people haven't updated their android facebook app?).
My app settings:
I'd post code, but this seems to be pure integration and configuration issues.
Note: my app isn't published on Google Play, could that be the issue?
Also: maybe this is only testable on the device? My device is "in the mail" so trying to get this done with emulator as much as i can.
Update: Facebook told me that this requires the Facebook app 1.9.* which is not in the SDK. So, I got my hands on a device, and while I haven't solved it, at least the app bookmark functionality is working. Will update if/when I find the answer.
Update 11am: I finally got it to work!
I had to publish my app in the Play/Market.
Each time I tested, log out of FB-Android app, clear cache, and force stop. Acc.
to the documentation the bookmarks are cached. I also think the
facebook app-syncing occurs on launch, and never again. So if you
change anything in FB's app settings, you need to log out/clear
cache/stop for it to take in the fb android app.
Only one key worked, even though it says "hash" in the fb app settings, I think
my dev key was screwing things up. Double-confirm that your release
key is the same as the one listed in app settings.
The final secret sauce for me, was to turn off SSO and deeplinking, re-test
without anything set. Also, remove dev package from phone and
download from Play. (see: key mixups). then, I stepped back through
the configurations by first turning on SSO, testing, then turning on
the native deep linking.
Only works on real device, not emulator (unless you can get 1.9 installed on emulator, may work, did not go down that route to test)
Not sure if this matters, but it may: install app from Store/Play, not from Eclipse. Could be the key syncing thing.
I figured it out- involved doing the following:
I had to publish my app in the Play/Market.
Each time I tested, log out of FB-Android app, clear cache, and force stop. Acc. to the documentation the bookmarks are cached. I also think the facebook app-syncing occurs on launch, and never again. So if you change anything in FB's app settings, you need to log out/clear cache/stop for it to take in the fb android app.
Only one key worked, even though it says "hash" in the fb app settings, I think my dev key was screwing things up. Double-confirm that your release key is the same as the one listed in app settings.
The final secret sauce for me, was to turn off SSO and deeplinking, re-test without anything set. Also, remove dev package from phone and download from Play. (see: key mixups). then, I stepped back through the configurations by first turning on SSO, testing, then turning on the native deep linking.
Only works on real device, not emulator (unless you can get 1.9 installed on emulator, may work, did not go down that route to test)
Not sure if this matters, but it may: install app from Store/Play, not from Eclipse. Could be the key syncing thing.
Have you had a look at the troubleshooting tips for deep linking? (Sorry, have to ask.)
I'm wondering if perhaps the FB app on your device was not properly quit after the relevant setting changes.
I'm trying to write some apps using wikitude, and I'm having some problems running even the example.
I've put the sample ( BasicOpenARDemo ) that comes with the SDK inside eclipse and tried to run it, where I encountered the next error: "wikitude was not found on the system. Please press the ok-button to access the Android market and download wikitude."
First question- I don't understand- Why am I approached to download the utility when I have a standalone sample inside my eclipse? Doesn't the core files behind Wikitude come with the SDK or the sample itself?
The next question will be - after some googling, I've found that in order to install this "Android market" I need to follow the manual that comes in the 9th message in the next thread (the message that was written by ronni.rasmussen) -
http://forum.xda-developers.com/archive/index.php/t-529170.html
Well, I've followed it, and now when I try to press the OK button that comes after the "wikitude was not found on the system..." message, I get redirected to the Android market, where I find Wikitude, but when I try to download it- I get a "Download was unsuccessful. Please try again" error message. How do I fix that?
One more thing that I don't understand- How come it's written in this offline Android market that the available wikitude version is for android 1.5 and no longer maintained?
As you can see- I'm quite baffled here. Hope someone could clear this up for me.
I was with the exact same problem. The problem was that installing Wikitude from the market (following the link you provided) does not guarantee to have the system requirements supported in the virtual device, therefore it gives an error when you run the BasicOpenARDemo, if it let you install it at all.
The solution was creating an AVD with an GoogleAPI (it includes maps support, I used the level 10 API for Android 2.3.3, it didn't work for the level 8 API), adding the camera, accelerometer, compass, GPS, etc., support to the virtual device (I did this via Eclipse). Then I downloaded the .apk for Wikitude and installed it via command line (.adb).