iOS 13 and OneSignal Registration Issues

Solar2D iOS
#1

Is anyone else aware of an iOS 13 related issue with using OneSignal? I’m getting this error now in my enterprise Corona app (native but using Corona as UI)

Couldn’t read values in CFPrefsPlistSource<0x28327c900> (Domain: group.xxxxx.xxxxxxx, User: kCFPreferencesAnyUser, ByHost: Yes, Container: (null), Contents Need Refresh: Yes): Using kCFPreferencesAnyUser with a container is only allowed for System Containers, detaching from cfprefsd

2019-10-08 12:00:08.956405-0500 xxxxxxx[5211:2433529] ERROR: Error registering with OneSignal: Error Domain=OneSignalError Code=400 “(null)” UserInfo={returned={

    errors =     (

        “[“Identifier invalid format.”]”

The app builds and installs but won’t register any iOS 13 devices with OneSignal

Note: I am building in xCode 11

OneSignal posted this relating to iOS 13 challenges: https://onesignal.com/blog/ios-13-introduces-4-breaking-changes-to-notifications/

But it’s not specific to Corona / Native

https://github.com/OneSignal/OneSignal-iOS-SDK/issues/529 specifies that xCode 10 or below will still build and work for OneSignal iOS apps.

OneSignal has released some native source to the “fix” for iOS 13 building on xCode 11 - but it doesn’t help us Corona plugin users. https://github.com/OneSignal/OneSignal-iOS-SDK/releases/tag/2.10.1

Any insight here guys?

Thanks!

#2

Hi,

We have noticed this problem as well, occurs with 2019.3538 and xCode 11.1

Any information on a fix?

Regards,

Keetiz tech

#3

OneSignal maintains their own Corona plugin. I would suggest reaching out to them and ask them to update it.

Rob

#4

The token issue was fixed in our native SDK in OneSignal-iOS-SDK version 2.10.1. The OneSignal Corona wrapper / bridge SDK is still using an older version however. We will be updating the SDK soon to fix this issue.

As a workaround you if you build your app with Xcode 10.3 then iOS 13 devices will be able to register without an issue. This works as iOS 13 will detect how the app was linked and fallback to the old token format.

#5

Thanks for letting me know! I am downloading xCode 10.3 now as I’m building using 11 otherwise. Hopefully, this gets me through until the SDK gets updated.

#6

When do you expect a fix?

#7

@josh_OneSignal any update on this? Is this issue fixes in current oneSignal plugin?

Regards,

Usman Mughal

#8

@Rob I have question for you here. If a developer has custom backend and app uses corona notification plugin(https://docs.coronalabs.com/plugin/notifications-v2/index.html), That app would be effected with this change in iOS 13?

Usman Mughal

#9

I’m sorry Usman. I’m not clear as to what you’re asking about. We recommend that you use the notification-v1 plugin for iOS since the v2 is mostly support for the Firebase FCM system, which Google had hoped could work for both Android and iOS, but really hasn’t worked all that well.

Rob

#10

After some study, trial and error - and finally just throwing in the towel, the only way I got push alerts to work with Corona & One signal was to go back to xCode 10.3 and load the individual phone profiles as outlined here:

 

https://stackoverflow.com/questions/56521200/xcode-fails-to-build-on-real-ios-device-running-ios-13

 

It also fixed a receipt problem I was having with Corona enterprise (old build), and Apple receipt validation / truncation.

 

Everything builds the exact same once the support profiles are loaded.