Skip to content
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.

ITMS-90078: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. #9

Closed
markymc opened this issue Jun 17, 2019 · 6 comments
Assignees

Comments

@markymc
Copy link

markymc commented Jun 17, 2019

I just added this SDK to my existing RN project and put up a TestFlight build. I then received an email from Apple saying:

ITMS-90078: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement.

However, I don't want to use push notifications at the moment. Is there some way to avoid this?

@xnth97
Copy link
Collaborator

xnth97 commented Jun 17, 2019

Hi @markymc ,

Thank you for using Flurry! Could you please check the following:

  • Did you enable "Push Notifications" in Xcode's Capabilities tab?
  • Did you enable "Remote Notifications" in Background Modes?
  • Do you have .withMessaging(true) when initializing Flurry.Builder?
  • Did you call [ReactNativeFlurry enableMessaging] in native code?
  • Did you implement didRegisterForRemoteNotificationsWithDeviceToken: in AppDelegate?

Please let me know if the problem still occurs. Thank you!

@markymc
Copy link
Author

markymc commented Jun 18, 2019

@xnth97 Thanks for your quick reply.

Did you enable "Push Notifications" in Xcode's Capabilities tab?
Did you enable "Remote Notifications" in Background Modes?

No I didn't. I just double checked and they're both disabled.

Do you have .withMessaging(true) when initializing Flurry.Builder?

No, it's:

  new Flurry.Builder()
    .withCrashReporting(true)
    .withLogEnabled(true)
    .withLogLevel(Flurry.LogLevel.DEBUG)
    .build(FLURRY_ANDROID_API_KEY, FLURRY_IOS_API_KEY);

Did you call [ReactNativeFlurry enableMessaging] in native code?
Did you implement didRegisterForRemoteNotificationsWithDeviceToken: in AppDelegate?

No and no.

Please let me know if the problem still occurs. Thank you!

As nothing mentioned above needed to change, the problem still exists.

Thanks!

@xnth97
Copy link
Collaborator

xnth97 commented Jun 18, 2019

Hi @markymc ,

Thank you so much for your reply! Sorry for any inconvenience this may cause. We are investigating into this and will let you know once we have a solution.

@xnth97
Copy link
Collaborator

xnth97 commented Jul 1, 2019

Hi @markymc ,

We just released a version which contains the fix. Please upgrade and re-link the RN sdk

react-native unlink react-native-flurry-sdk && react-native link react-native-flurry-sdk

and type n while being asked if you need to integrate Flurry Push. This will guarantee that push related code won't be linked to your project. Please let me know if the problem still occurs. Thank you very much for your feedback!

@xnth97 xnth97 closed this as completed Jul 5, 2019
@markymc
Copy link
Author

markymc commented Jul 8, 2019

@xnth97 Thanks very much. We'll update to that then. 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@markymc @xnth97 and others