I am working on an iOS app which need to get push notifications(using GCM) from web service(Made of Python).
Currently the web service works fine with Android devices, but it reports Error=MismatchSenderId, when I check this error in the online doc, it suggests the sender_id and API_key are not matched. The thing is, as I understand it(could be wrong), for iOS SDK, unlike the Android's, it doesn't need sender_id.
The tricky part is I have no access to the web service yet(which the collaboration party claim the Android app works fine with it). Could anyone shred a light on what steps should I take to fix this issue?
THanks in advance.
Related
I have been using FCM flawlessly during one year in debug, release, and play store release. Recently, I have change my computer from a windows to a Mac and now I am not able to make it works in play store. I am able to get notifications in debug and release but not in a signing app bundle.
I am using same signing key from windows PC so I am not sure where the problem could be. Any clue or idea will be appreciated.
The react-native app I'm working on has been having this issue for quite a while, background notifications are not working in the production app. This only happens for the iPhone 11 as we've tested with the iPhone 8 (both devices were running iOS 13.3) in production and it received them, so I don't think it would have to do with production's APNs certs. We've upgraded to .61 as well as react-native-firebase 6 hoping that that might solve the issue but to no avail, tried adding APNs headers to the message as well as some other things but nothing seems to be working. Like I said this is only happening in production, we've tried with the 11 in dev and QA and both times we were able to receive notifications.
Is there something specific that is required for iPhone 11s when using Firebase Messaging? Is there any way to view real time logs in Firebase (ie the images of logs in this post), all I've been able to find in the Firebase console is aggregated data for the app. I would like to be able to send a test notification to a specific user on prod from Insomnia and see if it is failing, why it's failing etc.
Any help would be appreciated if any other info is needed please let me know. Thanks.
Android Management APIs are supposed to be "compatible with any device running Android 5.1 or above that has Google Play installed." I really want that to be true, but am having trouble with Android TVs. (Specifically, a NexBox A95x and a TX3mini I'm testing with.)
My stumbling point is how to enter the enrollment token into the device when provisioning it? I had no problem with a Samsung tablet. But, the Android TVs don't use the same startup wizard after hardware reset, so there doesn't seem to be an opportunity to trigger a QR reader, or manually enter the token. I've tried entering the enrollment token into Google Play app (in lieu of the email or phone number to log in), but no luck.
Any ideas or insight how to make this work? If anyone knows a definitive reason why this can't be made to work (e.g. Management APIs don't work on AOSP) that'd be helpful information too.
Clarification (Updated 26 Dec 2017)
Here's a minimal, complete, and verifiable example of the Google Management APIs. The Quickstart exercise from Google, themselves.
Problem: The Quickstart exercise doesn't seem to work with Android TV (tested on a NexBox A95x and a TX3mini). The blocker appears on this step: (Provision A Device). The Android TVs have their own setup wizards that do not accept an Android For Work enrollment token. (I have completed the Quickstart on a Samsung tablet without problem.)
Google's documentation says the Management APIs are "compatible with any device running Android 5.1 or above that has Google Play installed" so it seems these Android TVs should qualify.
Has anyone found a workaround to do complete the Management API Quickstart on an Android TV?
As far as I know the Android Management API doesn't supports Android-based OS's like Android TV, Android Wear, Android Auto or Android Things. It just supports standard Android for phones and tablets.
since I am new in the world of developing apps for watches, and the fact that it exists for smartphones the following frameworks:
Xamarin
PhoneGap
appcelerator
kony
Cordova
...
I wonder if there exists for watches apps similar frameworks? So that you code once but run overall.
Thanks
Edit 1:
At this day (12.05.2015) regarding to the answer of a nativescript maintainer here. I will go with nativescript to start writing app for wearables.
Cordova/PhoneGap apps don't work directly on the wearable devices/watches. Cordova/PhoneGap is basically a javascript API which can run on WebKit/WebView on all the mobile OS's. But the Android Watch and Apple Watch doesn't support WebKit and so the apps developed with Cordova don't work directly on Watch devices. But if want to extend some of the features from the existing Cordova app to the wearable app, you need to create the extension app in native language and the extension should be able to communicate with the paired app on the mobile device. The extension on the Watch will have only UI and the bussiness logic etc runs on the Cordova app on the mobile. It is possible to establish communication between these apps which will drive the display on the watch devices.
I am not sure about the other frameworks you listed above on how much they support wearable devices.
As #kiran and #NRimer have mentioned, these cross platform frameworks are relying on the WebKit/WebView which is the almost universal layer supported on every mobile device. They dont run directly on the device, but device runs WebKit platform that runs these cross platform apps. So comparing the capabilities of the native app with cross platform app, native app is bigger, because it can have a hands on device hardware related features. The thing particular to the smart watches is that they mostly rely on other smart phone device, and it uses it's communication protocols, that are hardware specific, and WebKit doesnt have its hands on it.
It depends on what you're looking to do with the framework. Watch apps build off data provided by their containing app. For example if you want to provide custom notifications on the watch, the app (or server for remote notifications) constructs them. When your watch app needs information, it makes a request to the containing app. Lets say you have a group of apps that you want to provide the same notifications or functions on each of their watch apps, you could make a framework that handles these functions for the containing app. As for the watch portion, think of it as more of a display of information provided. Unfortunately i dont think there's a way to generate frameworks for watch apps yet. If you're looking to have a lot of code within the watch app this might be more difficult but for simple display of information you should be alright.
I need some reference of device cloud provider where i can test my native mobile app developed. I have already found on one appthwack but was wondering if there are any better options.
Thanks.
Testdroid - http://www.testdroid.com/ - over 400 Android and iOS devices, some for free.