Console printing 🚨Airship Implementation Error🚨: Ignoring call to application(_:didRegisterForRemoteNotificationsWithDeviceToken:). Either takeOff is not called or automatic integration is enabled.

Follow

Hi there, 

I'm going to reach out to you via our support email so that we can further troubleshoot this without posting potentially private information here. Once the ticket has been made, you can respond there with further information. 

Best wishes, 

Frenchy F.

Technical Support Engineer | Airship | New York

Found the fix. Just had to put the following key in config as false:
isAutomaticSetupEnabled = false

while i hface this issue i found out the support and they are pretty helpful clearing all the stuff for me 

Possible Solutions:

1. Ensure takeOff() is Called:

   • Verify that Airship’s takeOff() method is being called when the app launches, typically in AppDelegate.swift inside the application(_:didFinishLaunchingWithOptions:) method. Without this, Airship won’t initialize properly.
   import AirshipKit func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { // Initialize Airship Airship.takeOff() return true }

2. Check for Automatic Integration:

   • If you’re manually handling push notifications, you need to disable Airship’s automatic integration. This is because the SDK might be overriding your manual implementation of push notifications.
   • To do this, add the following line to the AirshipConfig.plist file:
   xml

    

   <key>com.urbanairship.automatic_setup_enabled</key> <false/>

   This ensures that automatic handling of push notification registration and other functions is disabled, and you can manage them manually.

3. https://menuspricesph.com/wendys-menu 

If you encounter the error message 🚨Airship Implementation Error🚨: Ignoring call to application(_:didRegisterForRemoteNotificationsWithDeviceToken:), it means the Airship SDK isn't properly initialized before processing the gbapp device token registration for remote notifications. This issue often arises when the takeOff method is missing from your app's launch sequence, which is essential for setting up Airship correctly. Alternatively, it could be due to automatic integration being enabled, causing the SDK to take control of this process on its own.

To fix this, ensure you call takeOff in the application(_:didFinishLaunchingWithOptions:) method if you are managing the setup manually. If you prefer automatic integration, check your settings to confirm that it is either fully enabled or correctly disabled to avoid any conflicts.

Airship Implementation Error🚨: The SDK is ignoring the call to application(_:didRegisterForRemoteNotificationsWithDeviceToken:) due to improper initialization. This error usually arises when the takeOff method isn't called during the app launch process, which is essential for setting up Airship correctly. Alternatively, if automatic menus is enabled, the SDK may be handling registration internally, leading to this issue.

To resolve this:

1. If you're managing the setup manually, ensure you call the takeOff method in application(_:didFinishLaunchingWithOptions:).
2. If automatic integration is intended, verify that it’s fully enabled in your settings to prevent any conflicts.