PushWoosh example code says 'registration successful' but prints only 32 characters token, should be 64

[henrik5]

Actually I don’t know this, I just know I copied the token in the message from my app and the Add Test Device form on Pushwoosh rejected the token.

Certificates and dev provisioning profiles are set up correctly so that the app asked me to allow the app the receive push notifications or not, and as mentioned the listener reports registration successful to the Pushwoosh server.

I’m asking here because chances are some of you know what’s up and how long the token should be and an example of its format for the Pushwoosh site to let me add the Test Device. I don’t want to chance it and publish the app for production until I’ve gotten a test push through on Iphone. On my Android phone it gets through, and it was dead easy in comparison to Iphone.

[george18]

The token should look something like like this: “35fd86e2c3d7cb3861f416390a019ee53542b883525e0f9fb42fe636c8adef39”

If you paste that code you’re using for PushWoosh registration I can hopefully help more.

[henrik5]

It doesn’t, as mentioned it’s 32 characters. I found out that what you can do is convert string to hex manually and then of course it doubles to the expected 64-character string. I didn’t see that in any docs, or the question would have been unnecessary.

For Android, it should be a humongously long string (for most people it seems to start with the characters APA).

The Corona example uses outdated url parameters in its POST request, instead use the PushWoosh example and fix the errors in it. Don’t forget to print out the device token (PushToken) to console. A tip is to send an email with the device token. At least I didn’t see registered device tokens appearing in some list on PushWoosh.com.

Another tip is that unless you can get distribution profiles installed manually on the Iphone, you can’t really test the version that you’ll upload to App Store. When you test the Iphone, you have to use the Woosh button rather than the Test Woosh. Expect no push to arrive if it doesn’t say > 0 subscribers. Android just works. Even with 0 subscribers and whether in sandbox or production mode.

All these are impressions from doing it for the first time.

[george18]

The token should look something like like this: “35fd86e2c3d7cb3861f416390a019ee53542b883525e0f9fb42fe636c8adef39”

If you paste that code you’re using for PushWoosh registration I can hopefully help more.

[henrik5]

It doesn’t, as mentioned it’s 32 characters. I found out that what you can do is convert string to hex manually and then of course it doubles to the expected 64-character string. I didn’t see that in any docs, or the question would have been unnecessary.

For Android, it should be a humongously long string (for most people it seems to start with the characters APA).

The Corona example uses outdated url parameters in its POST request, instead use the PushWoosh example and fix the errors in it. Don’t forget to print out the device token (PushToken) to console. A tip is to send an email with the device token. At least I didn’t see registered device tokens appearing in some list on PushWoosh.com.

Another tip is that unless you can get distribution profiles installed manually on the Iphone, you can’t really test the version that you’ll upload to App Store. When you test the Iphone, you have to use the Woosh button rather than the Test Woosh. Expect no push to arrive if it doesn’t say > 0 subscribers. Android just works. Even with 0 subscribers and whether in sandbox or production mode.

All these are impressions from doing it for the first time.