react-native-carplay: [QUESTION] App crashes when activated on CarPlay simulator, complaining about missing scene delegate

Hi, I’m using 2.0.0 with RN 0.64.2 and Xcode 13 to test on the iOS 15 simulator. I’m fairly sure I’ve implemented everything according to the sample app, entitlement is present and I do nothing fancy but displaying a “Hello World” screen. Still the app crashes as soon as I tab the app icon in the CarPlay simulator: 'NSGenericException', reason: 'Application does not implement CarPlay template application lifecycle methods in its scene delegate.'

I already looked into implementing the needed delegate but I wonder why it runs without all this in the example app in the first place. Thanks for any hints!

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 2
  • Comments: 25 (2 by maintainers)

Most upvoted comments

ITS COMING 💡

@birkir : Is it possible to use ^2.3.0 with a classic AppDelegate.m somehow? When doing so, I hit this crash. However, I don’t want to switch over to an AppDelegate.swift for the same reasons that @gavrichards mentioned in #132 (e.g. wanting Siri and other launchOptions).

Would any of the maintainers / contributors be able to investigate further why it appears that this package requires the com.apple.developer.carplay-maps entitlement even when you’re not using Maps? This seems like a fairly critical flaw, and is preventing me from being able to use the package. Thanks!

@gavrichards Did you solve with AppDelegate.m?

No, we switched to the new version that uses a Swift AppDelegate and Scene delegates: https://github.com/birkir/react-native-carplay/issues/68#issuecomment-1227095299

Hi there. I have same issue. It’s also works also with maps entitlement, but it’s not. So it will be cause problem on publishing, as I understand. So how to resolve it’ anybody understood? Thanks in advance.

It was revealed in another issue that this is because react-native-carplay requires the com.apple.developer.carplay-maps entitlement, even if you’re not using Maps. It’s definitely a bug.