OneSignal load time

[kamendo]

Can I do something about this (delay initialization may be?) Its slowing my app startup time :)

[Formerly]

I also have the same problem, trouble handling as soon as possible. Thank you.

[bank18651]

I also got this too.

[Nightsd01]

Most of this load time is due to our SDK’s interaction with the Objective-C runtime which can be a bit slow. We do a lot of swizzling so that developers don’t have to add a lot of boilerplate code to their apps.

I will look into how we can make this more efficient and perhaps delay it so that it doesn’t block initialization of the app itself.

[chrismanderson]

One potential solution is to let devs use the SDK without swizzling. I've asked this on the intercom in the past and seen other discussions around it but always seem to get back "swizzling is fine" 😁. I use Segment for my OneSignal integration precisely because this SDK swizzles.

If swizzling does cause startup time issues, seems like a prime opportunity to build in the functionality to allow it to work without it.

[revolter]

Being able to manually initialize the SDK so it doesn't rely on swizzling would be great!

[rgomezp]

Closing issue. Note: request still under consideration

[alexandre-g]

Hi, any updates on this? Getting OneSignal : 500.26 milliseconds init time on last gen iPad Air.
Apple's recommended is 400ms for the whole app.