APNs authentication key (.p8)
I have tried sending to only iOS devices from the firebase console and also by topic however nothing is getting to the device. I have used p12 successfully in the past.
I have added the GoogleService-Info.plist file to the app and deployed to the App Store.
I am using #capacitor-community/fcm in the App and have followed the instructions here:
https://github.com/capacitor-community/fcm#certificate
I am testing in production as it didn’t work in dev with a provisioning profile.
Everything works ok for Android.
Any suggestions on how to troubleshoot?
UPDATE:
I have also tried following the instructions here however the code errors in Xcode at Messaging.messaging().apnsToken = deviceToken:
https://capacitorjs.com/docs/guides/push-notifications-firebase#add-initialization-code
I got it working by following this guide:
https://devdactic.com/push-notifications-ionic-capacitor/
There are some differences in the Podfile and AppDelegate.swift otherwise it is pretty much the same.
Related
Firebase account I could not get crash in iOS production app. I have added 2 build variant in application. Beside firebase console production iOS application is detected but crash is not showing.
I have uploaded dsyms File using terminal. If any one know about this issue then please help me.
I have uploaded dsyms File using terminal.
I have a commercial macOS app I distribute in the Mac App Store. Now at startup I check for the App Store receipt and exit with code 173 if it is not present. This brings up the App Store sign in dialog in order to get a receipt.
I have always tested this with sandbox accounts but now I only get errors when I try to sign in with a sandbox account (or my real Apple ID).
The issue emerges when I start from XCode as well as when I export the app as a development build.
I have the following setup:
macOS 10.15.1
XCode 11.2
App signed with valid development certificate
I have tried the following:
Sign out of App Store app
Restart Mac
Tripple verified email and password
Create new sandbox user in App Store Connect
Ran codesign -vvvv which reports everything is fine
I do, however, see the following error on the Console, but could not figure out what it is supposed to mean:
StoreLegacy: Failed to perform in-line receipt renewal for application
at path /Users/me/Library/Developer/Xcode/DerivedData/MyApp-alwjuasqcasdfaufnnxhqeoo/Build/Products/Debug/MyApp.app :
'Error Domain=com.apple.commerce.client Code=600 "(null)"'
Has anybody seen this before?
Update
It works as expected on Mojave. So I assume this is an issue with Catalina.
#codingFriend1 - Thanks. I should have posted the workaround. It seems the problem was that I'm in the UK and my test account was with the UK app store. I created a new tester with the US app store and that worked.
The resulting certificate works with UK tester. I don't think it used to be like this, but hey ho!
It was this that finally got it working for me but there may be other problems.
I'm added Crashlytics for my iOS app. I downloaded framework from it via their site link, and went through all the steps for integrating the frameworks, adding the run script, etc.but problem is that i add framework in manually and not receiving a email.
Did you follow the instructions mentioned here to manually add the Crashlytics SDK?
Did you also integrate the Firebase SDK?
To use Firebase Crashlytics, you also need to install the Firebase SDK along with the related configuration. E.g. Installing the GoogleService-Info.plist file and the initialization code.
Once you do this, you will need to cause a crash. For this, you need to run the app, stop Xcode, and from the device run the app and cause the crash. Then you will need to run the app again from the device. If everything was done correctly, then you should see the report in your Crashlytics console.
I've setup OneSignal Ionic SDK to work with my Ionic 3 project.
Its finally registering devices in the console. However, when I archive and export the project from xCode to desktop, then run the project on a real device in browserstack (since emulator/simulator is not supported) - I get the following error (in console under users):
(Missing Push Capability)
The push capability is definitely there, as its enabled and I had been using Firebase Cloud Messaging - though had to migrate.
I'm just wondering if I'm missing anything here or is this a bug with OneSignal?
Many Thanks,
Kieran
that's the cause of the App Store rejection. If your ad-hoc provisioning profile has the aps-environment key, it means your app is configured correctly in the Apple Provisioning Portal. All you need to do is delete the App Store distribution profile on your local machine, then re-download and install the distribution profile from the Provisioning Portal. This new one should contain the aps-environment key.
We have created project in Mobile Hub and manage AWS Pinpoint to send push notification in iOS devices and setup AWS Pinpoint console for push notification. We have uploaded development certificate .p12 and download the demo app from our application(project) which is created using 'AWS Mobile Hub' web service(Screen shot attached). We are getting notification while installing it from adhoc IPA. But, We are unable to get notification when we are installing directly from Xcode into my device.
So, how to get notification when app install/run directly from Xcode ?
Thanks
Previously, the Pinpoint console didn't support sending push notifications via the APNs Sandbox development environment.
Note: This feature was supported earlier only by invoking the API (not through the console). You can make a call to the API to do the following:
To register the APNs Sandbox Channel.
Register a device as an APNs Sandbox endpoint.
Send messages/campaign pushes to it.
As of yesterday (10/03/2017) Pinpoint fully supports APNs Sandbox environment through the console as well. In order to register a device as an APNs Sandbox endpoint, use the latest version of the AWS iOS SDK (v2.6.2 or above) and enable the debug flag. This corresponds to the Sandbox development environment.
You can enable the debug flag by using the following code snippet
AWSPinpointConfiguration *config = [AWSPinpointConfiguration defaultPinpointConfigurationWithLaunchOptions:launchOptions];
[config setDebug:YES];
AWSPinpoint *_pinpoint = [AWSPinpoint pinpointWithConfiguration:config];