Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rich media page Forbidden 403 #47

Closed
apo1981 opened this issue Oct 18, 2016 · 8 comments
Closed

Rich media page Forbidden 403 #47

apo1981 opened this issue Oct 18, 2016 · 8 comments

Comments

@apo1981
Copy link

apo1981 commented Oct 18, 2016

Hi

I have updated to new version of sdk (4.9.0) because the pushwoosh library I was using (old one - jar version) does not receive any push notification anymore (compatibility issues????)

So, I have been forced to update to the latest version, and now I receive normal push notifications where the action is open the app.

However, when a push notification is sent with a rich media page, and the notification is open, the rich media page is not open and the 403 Forbidden message is show on the screen. This does not happen with the old sdk version I have integrated.

Why is this happening?

Thank you

@shaders
Copy link
Contributor

shaders commented Oct 18, 2016

Can you tell me the message ID or App Code so I can take a look in the system what was going on?

@apo1981
Copy link
Author

apo1981 commented Oct 19, 2016

Thks @shaders, this is the app code id = B713A-E3EF8

@apo1981
Copy link
Author

apo1981 commented Oct 19, 2016

Let me add the following information. I have tested with different version of the library

  • v4.8.2: push notification is received and rich-media CORRECTLY open
  • v4.8.3 (API change): push notification is received, but rich-media NOT correctly open (403 Forbidden)
  • 4.9.0 (latest one): same as v4.8.3

@DimanAM
Copy link
Collaborator

DimanAM commented Oct 19, 2016

There should be nothing related to rich media in 4.8.3 release.
Does this problem appear on any/specific device?
Does the problem persist if you clear application data?
Could you please attach device logs when push notification is received and opened?

@apo1981
Copy link
Author

apo1981 commented Oct 19, 2016

@DimanAM
Does this problem appear on any/specific device? Any device
Does the problem persist if you clear application data? We have uninstall and install the app again, and the issue persist

@shaders
Copy link
Contributor

shaders commented Oct 19, 2016

I've got this reproduced. Should be fixed soon, I'll keep you posted.

@apo1981
Copy link
Author

apo1981 commented Oct 20, 2016

Thank you @shaders
I will integrate v4.8.2 atm, and will wait for your fixed

fleurdeviande pushed a commit that referenced this issue Oct 21, 2016
Fixed:
    Incorrect base url for html pages [ISSUE47](#47)
    /setTags respose parsing error [ISSUE46] (#46)
@shaders
Copy link
Contributor

shaders commented Oct 21, 2016

Fixed in b115a2d

@shaders shaders closed this as completed Oct 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants