android 13 notification permissions request fired automatically too soon

[cjmaroney01-sams]

I work on a large app that uses MParticle and Urban Airship, hence this integration. I am working on setting my targetSDK to 33 and am using an android 13 emulator. I find that if I include the dependency for this integration, and call MParticle.start() in my Application.onCreate(), that the system fires a permissions dialog for notifications. Unfortunately, this dialog fires early in the launch sequence, and is auto-dismissed when the app finishes launching. I am unable to find out what I am doing to trigger this dialog, as I have commented out most of the Particle and UA stuff while tracking this down. I do not call
MParticle.getInstance()?.Messaging()?.enablePushNotifications()
or
UAirship.shared().getPushManager().enableUserPushNotifications()

anywhere, and I don't have a MPService or MPReciever anymore (commented out). All I am doing as far as I can tell is calling MParticle.start() -- if I take that call out, the notification dialog goes away, and if I comment out the implementation() of the urbanairship kit dependency so that it is not used anymore, the notification dialog goes away as well, even if I call start().

I really need to be able to control when this notification permission dialog launches so that I can show it at an appropriate time, and also so that it will not auto-dismiss and be useless anyway. Any hints would be appreciated.

[rlepinski]

I don't think mParticle can do anything about this ATM, but the Airship team will add a flag to disable this behavior in the next release, then post an update here.

[cjmaroney01]

ok great thanks.....is there an expected time when that release will likely happen?

[rlepinski]

The Airship SDK update will go out early next week and then I can submit a PR for this. I am not sure what mParticles release cycle is though.

[rlepinski]

#149