I have created a APP using GCM which works correctly on Android platform 4.1 and 4.03 (I.e. Gets a RegId and register itself in my server and can even recieve a GCM), but when I start the emulator for android 2.3 (API 10) then the app gets installed but never registered I.E never gets RegId. When I start (install) the application for the first time then it receives a GCM message which I do not understand where it comes from but I can see that the device is not registered in my server. I also used a HTC phone with 2.3.3 android software and stil same result. Can any one see what the problem might be?
On the emulator it should normally not work, because it will not have a google account tied to the device. It is requiered for a device to have a google account and Google Play installed to register for an id.
The phone on the other hand should work.
GCM will Work from Android 2.2.
Refer this tutorial it may help you,
http://androidv5.wordpress.com/2012/08/15/how-to-implement-google-cloud-messaging/
it works fine for me.
Related
Please, I'm using Android services in my app to launch local notifications, exactly as described here, on Appcelerator Wiki. The services run well as expected but if the application is removed from the recent apps tray or device was rebooted, services stop.
I would like to the service still running after the app is removed from the recent apps tray or restart service after reboot device. How can I do it using classic Titanium.
In iOS version of my app I'm using Ti.App.iOS.scheduleLocalNotification and run very well, even after switching the device off and on. I wish that on Android worked the same way.
Thank You for any help.
(sorry for my bad english)
You can try benCoding.Android.Tools module. check the BootReceiver
you can find an example here if you are using a service for notification you need to install the module and add the receiver to your tiapp.xml as in the example
My sample app using GoogleFit API of GooglePlayServices runs on Android mobile (using Android-M) but the same sample app gives error as API_UNAVAILABLE on Android TV (using Android-M) even though PlayServices version is latest version on TV.
My intention is to only to READ the Google-fit data.
Is it so that device like TV might not have health/fitness sensors and hence GooglePlayServices does not enable Google-Fit API (even though an application might be only interested in reading data)?
Any pointers available on this on how to enable GoogleFit APIs on Android TV?
EDIT1
Tried with 365 Body Workout apk https://play.google.com/store/apps/details?id=com.peirr.workout.play&hl=en on AndroidTV having latest GooglePlayServices [11.5.09 (836-164803921)] and found that it does not work as indicated in the below picture
I'm previewing the MobileFirst app (Cordova) on both browser and iOS Emulator but there doesn't seem to be any response when I call WLAuthorizationManager.obtainAccessToken().
I've tried to allow cross origin request but still face the same issue. Does anyone have any suggestions for what I should look at?
I had a similar issue on the iOS emulator. I even used Wireshark to see what was happening and the app never fired the authorisation request.
In the end I found that if you're running XCode 8.x, you have to enable keychain sharing by selecting the project -> Capabilities -> Keychain Sharing, and setting it to On.
After that I had to register the app again and all worked fine.
Make sure when you register or push the app and you're prompted for the version number, that you enter x.x.x instead of x.x - otherwise the server will not recognise the app.
Another thing to double check is the mfp:server runtime and url values in the config.xml file, if your pc's ip address has changed then the url value could be incorrect.
In iOS6 I used to install some of my apps over an adhoc network without internet sharing. So the iPad had no internet connection. Therefore I use a typical html and plist file. Everything was alright.
Now, in iOS7 the installation is not working anymore. It is just stuck in "Waiting" and nothing more happens. (Note: It is still working on my iOS6 iPad)
First I thought something might be wrong with my plist, but then I copied the files to my IIS Server and installed it from there. Here I had a internet connection on my iPad and everything worked out.
Is it possible that the wireless distribution now needs an internet connection in iOS7 e.g. to check the ipa in the app store or something like that? Because this is the only difference I can see.
The app is signed with a valid distribution profile.
Thanks for your help.
It turned out the installation of apps over the air in iOS 7 really needs an internet connection now. The iPad tries to contact at least the following URLs before installing the app.
ax.init.itunes.apple.com: The device obtains the current file-size limit for downloading apps over the cellular network.
ocsp.apple.com: The device contacts this site to check the status of the distribution certificate used to sign the provisioning profile.
It seems in iOS6 it was ok if those URLs were not reachable and now in iOS 7 they have to be reachable.
Well i just had the same problem and I figured it out. At least on my xcode this is what happened. Turns out the application target release code siging identities auto set to developer and not their current state, from xcode 4.x, which is distribution. So when I went to distribute my application I kept getting the same error you had. So Click on your project name in your project explorer then click on the application target, not the project, and make sure the code signing identity is not set to developer for your releases. I have no idea why the code signing identities were automatically set to the developer profile, maybe there was some sort of bug when updating from xcdoe 4.x to xcode 5 that caused this. But now other devices are able to install the program. Hope this helps.
(e.g. the Chrome browser for Android)
Talking about factory defaults here, not what users can install later.
(Sorry if this is a stupid question, I just can't find an answer anywhere)
Typically consumer facing Android devices do come with the browser. It is part of the core platform.
However, there is nothing stopping a manufacturer from removing the Browser for whatever reason. For example, that Android powered watch will not come with a web browser.
Yes, as it's part of Android OS.