I have updated my devices to iOS 10.1 and somehow the push notification has stopped working. I still have a device on iOS 10.0.2 and I still receive notifications and silent push on this one.
I am working with xCode 8 and swift 3. I have implemented the required iOS 10 methods for swift and cannot really figure out what has changed with this update. Could not find any push related changes here too: https://support.apple.com/kb/DL1893?locale=ja_JP&viewlocale=en_US.
Is there some other documentation/release notes maybe that I am missing here ? Anyone else facing the same issue ?
Any help is appreciated. Thanks!
Related
I updated IOS SDK to 14.4 and MAC OS also been updated.
All of a sudden FCM stopped working, it was working perfectly fine.
I am not understanding what exactly went wrong.
1.Since, fcm token is been triggered and registering in database as well.
2.Tried triggering from firebase console but still unable to receive notification, but in android it works fine.
3. Tried to trigger from our backend application (Dot Net), it gives Success:1 Failure:0
plugins used are cordova-plugin-fcm-with-dependecy-updated
import {FCM} from "cordova-plugin-fcm-with-dependecy-updated" declared in app.components.ts
Any help, will we be much appreciated.
I solved this problem in android studio by creating my custom notification handler and just inputing the data firebase sends. But I can't seem to find a way/guide/tutorial to do so with ionic.
Is there a way to do that or do is it only possible to show notifications when app in background?
I've tried every guide I found online but most of them just do nothing or the notification is just showed when app in background.
Thanks
Update: 23 July 2019
The reworked implementation has been released as cordova-plugin-firebasex#6.0.0.
See the documentation for more info: https://github.com/dpa99c/cordova-plugin-firebase
Original answer
This is something I'm working on in cordova-plugin-firebasex (my fork of cordova-plugin-firebase).
Currently it's a work in progress (first draft implementation done for Android on the dev branch) and I'm working on the iOS implementation.
You can test it out using the dev branch of my test harness project.
Hoping to have a releasable version in the next week or so.
I have stepped through all the steps here twice over.
https://github.com/flutter/plugins/tree/master/packages/firebase_messaging
I even deleted and re-paired my android package with FCM.
I have the right intent added to the manifest xml... and double checked it.
I have tried both on my Android Emulator, and my Actual Google Pixel.
I don't ever see an android notification.
Any assistance is greatly appreciated.
I'm using
Android Version - 9.0 (Pie) - API 28
Emulator Version - 28.0.16-5112988
It's a fresh emulator.
[EDIT]
I am now able to get notifications to my actual Google Pixel, but still not the emulator.
Thank you.
I have searched around and have not found the particular answer that I am seeking for. I just went and updated my App to a Swift 3 Language from swift 2. It obviously threw out a host of errors which I went through and fixed to the best of my abilities and now I do not have any errors. I can run the app but I cant tell if anything else is working because the Login or Auth sections of the app are not working. I know that I can just bypass to test but I have been working on it a lot and trying to get this feature to work that worked well before the language was changed..
Very simple my question is this:
I upgraded to Swift 3. Do I need to upgrade the cocoa pods to support the change in language? If not is it just an issue with the way that my code is and because of the change to swift 3 that i need to keep tinkering with?
Thanks for any help
sorry posted that about 12 hours to early. After doing a lot of research it looks like I found the answer. have not tested yet but I think I am getting the same errors in the compiler.
"We've noticed what seems to be an issue with the latest iOS 10 simulators (up to beta 6 at the time of this writing) that causes Firebase Auth to throw an error due it to not being able to write values to the keychain. This issue does not affect real devices." This is from a Firebase Blog
Hello I got this problem on the device and not on simulator, my device is iOS 9.3.3 and the strange thing is that when run from xcode it works just fine
But when I open from device after stopping debug from xcode, the error will occur
And after some digging, I found out that if pod is only using firebase, it connect just fine even opening from the device
But if I add just 1 pod, it will error like above, so I don't really understand what is going on
And yes already try using keychain sharing
Any tips?
Edit: it works fine on other devices running iOS 8.1
I have a new iPad Air 2 running iOS 8.1 that I am using to test my app.
The call to URLForUbiquityContainerIdentifier never returns.
I installed iOS 8.1 on my iPhone 5s and everything works as expected.
I am thinking there may be a bug in iOS 8.1 for the iPad Air 2 but I am not sure. I noticed that in Settings for iCloud that Documents and Data wasn't even listed, and I signed out and signed back in and Documents & Data showed up in settings. That leads me to believe that this might be an iOS bug.
But in case it is not, is anyone else had the call to URLForUbiquityContainerIdentifier never return? If so, what did you do to fix it?
This is a Core Data app using iCLoud storage for an sqlite data store.
I call ubiquityIdentityToken before and it retuns a non-nil value, so iCloud is available.
NSURL *cloudStoreURL = [fileManager URLForUbiquityContainerIdentifier:#"XXYYZZ.com.yourcompany.appname"];
A user emailed me and said it suddenly started working for him. I just ran my app with no changes and everything works as it should. I do not know why it is working, but something changed somewhere, my guess is Apple changed something.
I've seen the same issue recently for one of my apps. It never occurred directly for me but it has occurred for Apple during the review process. However, it happened only for one of my apps. A second app with the same code never showed the issue for myself or for Apple. I have contacted DTS regarding the problem. If I get a solution I'll post it here.