Hi guys I'm working on app where I've to save FCM in mobile locally. It's working fine in foreground message but it's not working on background and terminate state.
Related
We are developing a chatting application and for chat, we are using react-native gifted chat and react native image picker for it. when running on both ios and android simulators they are running perfectly but when we run the app on android mobiles we are encountering an image upload not opening issue and a chat disabled issue, we are unable to chat on that and after that, we have changed the target version on build.gradle file and image upload working perfectly but we are unable to chat.
Is it possible for setBackgroundMessageHandler to be launched only when the app is in background state and not from quit state?
I have recently updated react-native-firebase package to v11, and I noticed there is some delay for setBackgroundMessageHandler to launch when in quit mode.
This can cause some race condition in my app between the headless task and the app being launched when the user press the notification message (on android).
If not possible, is there some indication that setBackgroundMessageHandler launched from background state and not from quit state?
My flutter project is using firebase_dynamic_link package. I followed the instruction to register both my android and ios app on the firebase console without any problem. I've tested it out on android and it's working fine, opening the app I have running.
On iOS, I was expecting it to open the app I have running on it, instead I just get redirected to a preview page link.
Is it not opening my ios app because :
It's not yet published on the app store ?
Or is it because of an error in setup?
You can disable it in Firebase Console when you create/edit the dynamic link.
Hi all I am new to iOS development, I have put in the deep end to get push notifications. I found pushsharp and was using this tutorial
Tutorial I a using
I have used a windows application instead of web application and added the latest pushsharp. The code build and runs and I can get the push notification but only on sandbox.
I build my iOS app
Open the ipa on my iPad in xcode to install
once installed open the app and select allow to allow remote notifications
Get the device token when the app is opened and stick it in my winforms app
send a push using push sharp and bada bing bada boom it works like a charm.
I want to be able to use my production certificate as well. So I created a provisioning profile for App store. Created a signing request, created a certificate and in my provisioning profile section on apple portal i can see my new provisioning profile
I am able to build my iOS app successfully however when i try and install the ipa onto my ipad i get an error
App installation failed
a valid provisioning profile for this executable was not found
Is there a step which i have missed? Why do i get app installation error.
What will happen if I release a app which is using devcertificate to show push notifications?
You can't use a distribution provisioning profile to run the app on your ipad directly.
The iOS Distribution certificate can only be used to build an app that will be installed via the App Store.
You need to use either a development profile, or an enterprise distribution profile to install on test devices.
If you want to test a beat version, you can test the app using TestFlight.
Here are some way to test a beat version.
What will happen if I release a app which is using devcertificate to
show push notifications?
You have to use a production push certificate to push notification in release mode.
I am running the sample push notification hybrid project provided by IBM in windows phone environment. When the app starts, the screen with the four buttons loads up first. Is this the normal flow for the app or should the login page load first followed by the page with the four buttons ? I didn't face this issue while working on android environment.
The sample application for push notification does not come by default with the Windows environment. It comes with the Android environment.
To force the application to start with a login screen also on Windows you'll want to protect the application with a security test.
Open application-descriptor.xml, find the Windows environment element and add the following attribute: securityTest="your-custom-securitytest-name" (like the Android environment).