I found a work around, but not a solution. I think there is a bug in Thunkable TBH, as this feature was working on an earlier build, then stopped abruptly without any changes. Support where pretty useless.
How I resolved was:
Logged into oneSignal website and created an ‘In-app message’ for my app. This was set to display a push notification upon first run that asks users if they want to enable push messages with an action button.
-I Set the action button to ’ push notification prompt’
Same problem here. As I finally solved how to make my own P12 without the OneSignal provisioning tool and got my app approved on the App Store, I discover that the push notifications don’t work anymore due to this bug. Nice.
Indeed, @conroy33, would be nice if this was sorted soon. And please post here when it is. Thanks!
No, the provisionator tool is good for Apple – when it works. The trouble is that it wasn’t working a few days ago when I tried to use it. After reaching out to OneSignal they confirmed me that they’re currently having issues with it and directed me to create P12 manually, which I then did.
@ethosworkfi@Tommaso If you’re experiencing what you also think is part of this issue, go ahead and DM me a link to your projects–the more examples I can get, the more likely I will be able to get our engineering resources available to work on getting a permanent fix.
Just sent you a link via DM. I don’t know what’s mission critical for the team but to me missing iOS notifications is pretty high on the list (even though there’s this workaround). Hope this would get fixed soon. Thank you!
By the way, meant thank you @chay for coming up with the workaround. It’s better than nothing.