Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
Creating a mobile-spec project for Windows with:
./cordova-mobile-spec/createmobilespec/createmobilespec.js --windows --forceplugins
shows lots of errors like these during creation:
Access rules must begin with "https://", the following rule will be ignored: http://audio.ibeat.org Access rules must begin with "https://", the following rule will be ignored: http://whatheaders.com Access rules must begin with "https://", the following rule will be ignored: http://*.apache.org Access rules must begin with "https://", the following rule will be ignored: http://www.google.com Access rules must begin with "https://", the following rule will be ignored: http://google.co.uk Access rules must begin with "https://", the following rule will be ignored: http://techslides.com Access rules must begin with "https://", the following rule will be ignored: httpssss://example.com The following navigation rule had an invalid URI scheme and will be ignored: "httpssss://example.com". The following navigation rule had an invalid URI scheme and will be ignored: "cdvfile:*". The following navigation rule had an invalid URI scheme and will be ignored: "data:*". Access rules must begin with "https://", the following rule will be ignored: http://audio.ibeat.org Access rules must begin with "https://", the following rule will be ignored: http://whatheaders.com Access rules must begin with "https://", the following rule will be ignored: http://*.apache.org Access rules must begin with "https://", the following rule will be ignored: http://www.google.com Access rules must begin with "https://", the following rule will be ignored: http://google.co.uk Access rules must begin with "https://", the following rule will be ignored: http://techslides.com Access rules must begin with "https://", the following rule will be ignored: httpssss://example.com
Those also repeat when running the created project with `cordova run windows --archs=x86`:
Access rules must begin with "https://", the following rule will be ignored: http://audio.ibeat.org Access rules must begin with "https://", the following rule will be ignored: http://whatheaders.com Access rules must begin with "https://", the following rule will be ignored: http://*.apache.org Access rules must begin with "https://", the following rule will be ignored: http://www.google.com Access rules must begin with "https://", the following rule will be ignored: http://google.co.uk Access rules must begin with "https://", the following rule will be ignored: http://techslides.com Access rules must begin with "https://", the following rule will be ignored: httpssss://example.com The following navigation rule had an invalid URI scheme and will be ignored: "httpssss://example.com". The following navigation rule had an invalid URI scheme and will be ignored: "cdvfile:*". The following navigation rule had an invalid URI scheme and will be ignored: "data:*". Access rules must begin with "https://", the following rule will be ignored: http://audio.ibeat.org Access rules must begin with "https://", the following rule will be ignored: http://whatheaders.com Access rules must begin with "https://", the following rule will be ignored: http://*.apache.org Access rules must begin with "https://", the following rule will be ignored: http://www.google.com Access rules must begin with "https://", the following rule will be ignored: http://google.co.uk Access rules must begin with "https://", the following rule will be ignored: http://techslides.com Access rules must begin with "https://", the following rule will be ignored: httpssss://example.com Tests will use the following file transfer server address: http://rwswbpiopr.localtunnel.me
And as a result the automates tests using those URLs also fail:
