Posts made by jamal

@scarlet20,

See: https://stackoverflow.com/questions/34257097/using-handleopenurl-with-custom-url-scheme-in-cordova/34281420#34281420

@scarlet20, I assume you are using https://github.com/EddyVerbruggen/Custom-URL-scheme#readme

If so, read the Usage section and how to the write the handleOpenURL(url) method, which receives the URL that was used to launch your app.

See https://content-security-policy.com

@gwclubexpress,

Try adding https; after ‘unsafe-eval’.
So content="… ‘unsafe-eval’ https;"

HTH,
Jamal

@gwclubexpress, see https://monaca.io/headline/

Select “Configure -> App Settings for iOS” from the IDE header menu and update the item “WebView Engine” to “WKWebView”.
For the build environment, select the menu “Build -> Build Environment Settings…” and set “iOS 5.1.1” and “Xcode 11.3”.
Select “Configure -> JS/CSS Components Settings…” and update Monaca Core Utility to version 2.1.0

@gwclubexpress, what plugins are using?

Also, make sure you are using the latest plugins from their vendors.

Unfortunately, Apple does not report what plugins that still use UIWebView in your app when they return ITMS-90809.

@jeb62868, are you building your Android app for debug or distribution?

If for distribution, did you configure and import the KeyStore and Alias?

@danielfranz, I am not sure what you are trying to achieve and purpose.

Is the app native?

What is the app environment?

@johnd2323,

1. What plugins are you using?
2. Show your config.xml
3. Where you testing?

or better yet, upload a reproducible sample.

@maurovanetti said in ITMS-90809 warning by Apple: deprecated UIWebView APIs:

Re: ITMS-90809: Deprecated API Usage warning from Apple

I’m experiencing exactly the same problem. My app accesses the phone camera to scan a QR code.
Is the app bound to be rejected when the deprecation turns to end of support for this API? Can I replace the API by upgrading my dependencies?

I suggest your check for upgraded versions of plugins to make sure they are WKWebView compliant.

@emccorson said in Urgent: Error when build for release of an iOS app:

As per the above answer, you need to specify 2.7.0 for now @jamal

Just checking! When will you guys update to a new version of CocoaPods in the build process?

OneSignal is already at version 2.8.4 and there are bug fixes that may affect the functionality if not included in our apps.

@emccorson,
2.7.0 worked fine. Thanks!

@emccorson, I am encountering a similar issue using the latest onesignal-cordova-plugin. I am not specifying the version number, so I assume it’s pulling the latest version 2.8.1. I removed and installed the plug-in, it still fails.

Error log:

Discovered saved plugin “onesignal-cordova-plugin”. Adding it to the project
Installing “onesignal-cordova-plugin” for ios"framework" tag with type “podspec” is deprecated and will be removed. Please use the “podspec” tag.Running command: pod install --verboseFailed to install ‘onesignal-cordova-plugin’: Error: pod: Command failed with exit code 31
at ChildProcess.whenDone (/private/tmp/download/node_modules/cordova-common/src/superspawn.js:135:23)
at ChildProcess.emit (events.js:189:13)
at maybeClose (internal/child_process.js:970:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
Failed to restore plugin “onesignal-cordova-plugin” from config.xml. You might need to try adding it again. Error: Error: pod: Command failed with exit code 31

@powerdroid,

Please create a CodePen that shows the issue?

@cesarechazu,

jQuery:

$("#yourOnsListElement").empty();

Javascript:

var elem = document.getElementById('yourOnsListElement');
while (elem.firstChild) elem.removeChild(elem.firstChild);

or

var elem = document.getElementById('yourOnsListElement'); 
elem.innerHTML = '';

@originalnoob,

Use the following instead of custom-config-file block.

<config-file parent=“NSCameraUsageDescription” platform=“ios” target="*-Info.plist">
<string>Camera is used for scanning barcode</string>
</config-file>

Almost 2 years laters and SPAM and SCAM is still spreading on this forum!!
C’mon! Fix your forum!!

@rk, remove viewport-fit=cover from the meta name=“viewport” tag and see if this helps.