-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
bug: URL blocked by whitelist on Android #3597
Comments
With the updated version of cordova-android, you now need to include the cordova-whitelist-plugin. https://github.com/apache/cordova-mobile-spec/tree/master/cordova-plugin-whitelist Try adding that to your project |
Hi Mike, Thank you! It works now after adding that plugin. Thank you for your help. Ari |
Please tell me how to install this plugin and simple demo code to call it , |
for example: |
Thank you for your help , |
+1 thanks for the help. I needed the whitelist plugin to run my cordova app in android studio. Google search brought me here. |
+1 thanks |
+1 Thanks for the comments, I have installed and ran my app successfully! Yey! |
+1 thanks |
You need to upgrade to Cordova CLI 5.0 to get Cordova-android 4.0. Mike Hartington
|
Thanks Mike, I actually found that this worked also: |
Hi, This plugin requires cordova ios 4.0.0 but i can only find cordova ios 3.8.0 Thank you for your help |
@julienwikart Look one comment above yours - try running "cordova platform update android@4.0.0" from the command line. |
Unfortunately my question was regarding iOS 4.0.0 and not android... But I found the solution : |
cordova ios and cordova android both have separate release cycles. For cordova-ios, the whitelist plugin shouldn't do anything, sense it's not setup for it. |
how to solve the URL blocked whitelist issue while call weather api. Please help me to solve this issuse |
Thanks :) |
How did you configure the whitelist plugin to allow the access? Did you use allow-intent or allow-navigation? I can't get it to work with calling firebase server for authentication. |
@rszczypka all I had to do was add the plugin and the error was gone. No configuration, didn't even have to call or do anything with the plugin. this post provides an html header you can if adding the plugin isnt working for you: |
+1 Thanks installing this plugin removed redirect errors from my android app. |
thanks. it solved the issue |
I am working on meteor. I am also facing problem of URL blocked by whitelist I installed "https://github.com/apache/cordova-plugin-whitelist" plugin. But it is giving me error "Skipping downloading new version because the Cordova platform version or plugin versions have changed and are potentially incompatible". I had even tried different viresions also. Please tell how to resolve this issue |
@prachi708 meteor is locked to a particular version of cordova. Just install a specific version of whitelist with something like:
If you're using an older version of meteor (locked to an older version of cordova) you may need to play with the whitelist versions or update meteor. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Type: bug
Platform: android 4.4 webview
My environment: OS X Yosemite, cordova 5.0.0, ionic 1.3.20. I use Firebase to for Facebook Authentication service. In IOS things work fine, but in Android, during Facebook authentication, I got: "W/SystemWebViewClient( 1556): URL blocked by whitelist: https://auth.firebase.com/v2/intense-torch-3742/auth/session?&requestId=whdi3macji4xffd91e2qxh96ohwamqsu380f&requestKey=XnWG8sRju97nlg4RM2pZQofpyLu933FI&v=js-2.2.4&transport=json&suppress_status_codes=true". In my config.xml: "
". Also tried "". I have InAppBrowser plugin installed too. Any thought why I'm seeing the URL was blocked where it should not according to config.xml? I have also checked all other config.xml files and they look good to me - they allow everything.
The text was updated successfully, but these errors were encountered: