updating plug-in to one signal not working

Corona Marketplace OneSignal
#1

I changed the settings to the updated documentation on the onesignal site. I also went to the plug in directory and activated the plug in. Now when I go to build for device I get the following.

Build failed:

A device build error occurred on the server. 

BuildID: 5553dda0a3da3 

Error: You are not currently subscribed to the follow plugin.

Publisher: com.onesignal 

Plugin: plugin.OneSignal

Is there a delay between subscribing and the build server(s) knowing about it.

#2

Hello,

It should take affect right away. Can you verify that you used the same account when activating the plug on the directory page and the account in the Preferences menu in Corona itself?

Update: Just tried creating anther Corona account and added the OneSignal plugin. It seems there is a delay that I didn’t notice before in testing. I’ll update this post again after I time it.

Thanks.

#3

Is it working for you now? It just started working with a new Corona account I just created. It took about 20 to 30 minutes to activate for me. I didn’t have to restart the Corona Simulator.

Thanks.

#4

Sorry, not anywhere near my MacBook right now. Once I have a chance to test I’ll post here.

#5

OK, I checked this morning and the build proceeds just fine.

#6

Thanks, I am creating a guide to help newbies out:

http://fearby.com/how-to-setup-a-new-sandbox-corona-ios-app-with-push-notifications-with-onesignal/

I got stuck with the waiting 30 mins for the plugin to activate.

Build Failed

A device build error occurred on the server. 

BuildID: 55bfc1367ec16 

Error: You are not currently subscribed to the follow plugin.

Publisher: com.onesignal 

Plugin: plugin.OneSignal

#7

Hey FearTec,

Your guide looks great, that for creating it. Also we rebranded to OneSignal from GameThrive, still the same company.

The 30 minute plugin activation issue seems to be linked to if you add OneSignal to your build.settings before activating it on Corona’s plugin directory from what I have seen at least.

Thanks.

#8

Thanks, the issue was with Corona delaying the plugin activation on their servers and nothing to do with OneSignal.

#9

Hello,

It should take affect right away. Can you verify that you used the same account when activating the plug on the directory page and the account in the Preferences menu in Corona itself?

Update: Just tried creating anther Corona account and added the OneSignal plugin. It seems there is a delay that I didn’t notice before in testing. I’ll update this post again after I time it.

Thanks.

#10

Is it working for you now? It just started working with a new Corona account I just created. It took about 20 to 30 minutes to activate for me. I didn’t have to restart the Corona Simulator.

Thanks.

#11

Sorry, not anywhere near my MacBook right now. Once I have a chance to test I’ll post here.

#12

OK, I checked this morning and the build proceeds just fine.

#13

Thanks, I am creating a guide to help newbies out:

http://fearby.com/how-to-setup-a-new-sandbox-corona-ios-app-with-push-notifications-with-onesignal/

I got stuck with the waiting 30 mins for the plugin to activate.

Build Failed

A device build error occurred on the server. 

BuildID: 55bfc1367ec16 

Error: You are not currently subscribed to the follow plugin.

Publisher: com.onesignal 

Plugin: plugin.OneSignal

#14

Hey FearTec,

Your guide looks great, that for creating it. Also we rebranded to OneSignal from GameThrive, still the same company.

The 30 minute plugin activation issue seems to be linked to if you add OneSignal to your build.settings before activating it on Corona’s plugin directory from what I have seen at least.

Thanks.

#15

Thanks, the issue was with Corona delaying the plugin activation on their servers and nothing to do with OneSignal.