-
Notifications
You must be signed in to change notification settings - Fork 369
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
Egypt blocking OneSignal - OneSignal Android Studio failed to get Android Parameters issue #855
Comments
Howdy, |
I am located in Egypt. I found the problem but I’m unable to resolve. The problem is, if I go to my browser and try going to https://onesignal.com, it is just blocked. However if I try to go to https://app.onesignal.com it works fine and because the OneSignal API uses https://onesignal.com/.., it just gets blocked here. I tried changing networks and using LTE but the issue persists. I just need a way to change the BASE_URL of the api from https://onesignal.com/ TO https://app.onesignal.com/ |
Egypt is blocking OneSignal. We are looking into how best to communicate with Egypt on how best to resolve this issue. If you want to reach out to your ISP and let them know they should unblock OneSignal, that would be helpful. |
I tried contacting the ISP but they keep saying that it is not blocked. I will keep trying to contact them to hopefully get a solution to this. |
@mtm19 , |
@rgomezp |
Not sure if that would help, but at least in my case, in a new browser session when I go to https://onesignal.com and get an SSL error, if I then visit https://app.onesignal.com which loads just fine, it solves the problem with https://onesignal.com and I no longer get the SSL error for as long as the session lives. |
Hi everyone, unfortunately, this is something up to the ISP. I would encourage you to try to pressure them to unblock OneSignal. However, this isn't really an issue with the SDK so I will be closing the issue. Hopefully, this gets resolved soon |
@rgomezp A workaround could be communicating over a subdomain like api.onesignal.com instead of the naked domain. It seems to be working without any issues so far on TE Data. Would it be possible to do this in the Android SDK? |
I am from Egypt and I have the same problem any one find any Solution ? |
I'm facing the same problem from Egypt |
Please contact your ISP |
Any update on that issue please, we still have that problem in Egypt, as tested with We, Etisalat, Vodafone, currently all have that issue There is update to that issue please? Egypt's customers are highly affected |
@rgomezp Any updates about this issue. We are still facing it. |
It appears that subdomains of onesignal.com are not blocked by the Egyptian ISP TE Data (also known as WE) Fixes OneSignal#919, OneSignal#883, OneSignal#859, OneSignal#855, OneSignal#849, OneSignal#847
Description:
I am trying to integrate OneSignal to my android app after successfully integrating it to iOS with no problems. I have added android platform to my app in my OneSignal account and gone through all the steps. However, when I run the app, it just fails to get the parameters and returns userid = null, pushtoken is not null, permissionStatus.enabled = true, subscriptionStatus.subscribed = false. I have literally tried everything since 3 days but with no luck. It doesn't event recognize in the website that any device has requested but got an error. I have tried using simulators and real devices but it never worked. I have also tried to go to the link its trying to access through the computers browser and it gets the json data.
Environment
Android Studio 3.4.2 (Windows 10)
Android Studio 3.5.1 (Mac OS Mojave 10.14.6)
Pixel 3 XL Simulator running (Android 9, API 28)
Pixel 2 XL Simulator running (Android 8.1, API 27)
Huawei Honor real device running (Android 7.0, API 24)
OneSignal.sdktype = native
OneSignal.VERSION = 031104
Steps to Reproduce Issue:
Code
public class ApplicationClass extends Application {
}
OneSignal Logs
JSON Data
"chnl_lst":[],"outcomes":{"direct":{"enabled":false},"indirect":{"notification_attribution":{"minutes_since_displayed":1440,"limit":10},"enabled":false},"unattributed":{"enabled":false}}}
The text was updated successfully, but these errors were encountered: