-
Notifications
You must be signed in to change notification settings - Fork 114
Blocked in Egypt #871
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
Comments
We have many issues with Onesignal based domain is being blocked in Egypt you can check at iOS repo is been fixed may 2020 but in the Web SDK still some calls is called from the base onesignal URL this will result to fix issue OneSignal#871
Duplicate of OneSignal/OneSignal-iOS-SDK#554 |
Hello @rgomezp this is not a duplicate because the web sdk here https://cdn.onesignal.com/sdks/OneSignalSDKWorker.js still using the base url https://onesignal.com/api/v1/ but it should be updated to https://api.onesignal.com/api/v1/sync/ can we get this resolved in the web too ? |
Hello @rgomezp please take in consideration that the getOneSignalResourceUrlPath function in OneSignalPageSDKES6.js file needs to be changed to https://assets.onesignal.com, thanks. |
Uh oh!
There was an error while loading. Please reload this page.
Description:
as you may hear already Onesignal base domain is been blocked for 3 years or more now from many ISPs in Egypt, but any subdomains such as api.onesignal.com or app.onesignal.com are working fine.
but when I implemented your Web push notification SDK I see that most requests were made on api.onesignal.com but some requests are directed to the onesignal.com base domain which is a block.
Steps to Reproduce Issue:
Anything else:
this would be fixed if you completely changed all your SDK codes to be using https://api.onesignal.com/api/v1/sync/...... instead of https://onesignal.com/api/v1/sync/.............
The text was updated successfully, but these errors were encountered: