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.
Related
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.
I haven't had much success searching for this. I'm developing an Android Things application that will connect to a user phone to do certain things. I want to use this for delivering app updates as well.
So far, my crude searches on this have just discussed OTA via the Console and thus internet.
My gut has said that I could just build this - I could have a new version of the APK, transfer it to my device via bluetooth, and then just have the device copy it over the old one and reboot. But, not sure. I was hoping maybe there was an API for this and I'm just not wise enough to know how to find it via the searches.
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.
I'm developing and distributing a communication software for disabled people since years.
These handicapped people prefer to have everything in one application (eMails, internet, Skype, etc.).
Therefore I've used the Skype4COM library.
It all worked fine for years, then suddenly it wouldn't work anymore (I think it was in 2014), then shortly after, it worked again.
Now - using Windows 10 with the integrated Skype application - it doesn't work anymore.
I'm getting the error "Skype client is not installed" in this line:
Set oSkype = New SKYPE4COMLib.Skype'works fine
oSkype.Client.Start True, True 'raises error "Skype client is not installed"
I've tried to get some information about this on the docs, but I didn't find the required information.
Does anybody know what I might be doing wrong or what I have to do differently in order to allow the user to use Skype in my communication software again?
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.