[jira] [Commented] (CB-13273) Webview is sized incorrectly on iPhone X (Simulator)
[
https://issues.apache.org/jira/browse/CB-13273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208703#comment-16208703
]
ASF GitHub Bot commented on CB-13273:
-
Github user zhoupIT commented on the issue:
https://github.com/apache/cordova-plugin-statusbar/pull/85
@dimitri320 me too!
> Webview is sized incorrectly on iPhone X (Simulator)
>
>
> Key: CB-13273
> URL: https://issues.apache.org/jira/browse/CB-13273
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Affects Versions: cordova-ios 4.5.0
> Environment: Xcode 9.0 (9A235)
> Simulator 10.0 (SimulatorApp-829.6) - iPhone X
>Reporter: Dave Alden
>Assignee: Shazron Abdullah
> Labels: iPhoneX, ios11
> Attachments: Simulator Screen Shot - iPhone X - 2017-09-14 at
> 15.52.54.png, Simulator Screen Shot - iPhone X - 2017-09-15 at 09.20.48.png,
> Simulator Screen Shot - iPhone X - 2017-09-19 at 11.29.00.png, fig1.png,
> fig2.png, webview-test.zip
>
>
> New app with cordova-ios@4.5.0 (using default UIWebView) running on iPhone X
> Simulator does not size correctly, leaving black areas above and below the
> app content and white bars between the black areas and app content.
> Adding cordova-plugin-wkwebview-engine so Cordova uses WKWebView, white bars
> go away, but the black areas remain:
> !https://cdn.pbrd.co/images/GKeaEPg.png|height=640!
> !https://cdn.pbrd.co/images/GKeaWwK.png|height=640!
> Setting
> {code:html}viewport-fit=cover{code}
> fixes the white bar issue with UIWebView, as outlined here
> [http://stephenradford.me/removing-the-white-bars-in-safari-on-iphone-x/],
> but the black areas remain:
> [^Simulator Screen Shot - iPhone X - 2017-09-14 at 15.52.54.png]
> Attached Cordova project illustrates the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11244) Update Android Project Structure to be more compatible with Android Studio
[ https://issues.apache.org/jira/browse/CB-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208599#comment-16208599 ] ASF subversion and git services commented on CB-11244: -- Commit cd46bd5ee889c8e870fd709458748b3b68ecc72e in cordova-common's branch refs/heads/master from [~auso] [ https://git-wip-us.apache.org/repos/asf?p=cordova-common.git;h=cd46bd5 ] CB-11244 : added unit tests for ConfigFile This closes #8 > Update Android Project Structure to be more compatible with Android Studio > -- > > Key: CB-11244 > URL: https://issues.apache.org/jira/browse/CB-11244 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: CordovaAndroidSix, android-next > > Currently our existing Android projects have the old Android Project > structure created by default, even for new projects, which makes no sense > since we no longer support Eclipse as the default project editor and have > moved to Android Studio for Android development. > The main reason for doing this is to clean up dependencies and to allow for > projects and dependencies to work more like how modern Android projects work > and to remove as much custom Gradle code as possible. This would also allow > us in the future to move towards having Android Plugin code work as Android > Libraries with Resources instead of just copying things across, which gives > us the ability to add JUnit tests and bundled resources. This would > dramatically increase the quality of plugins such as InAppBrowser, and third > party plugins such as the Barcode Scanner. > This would have to be done on the next major version, and the upgrade would > be tricky to do. However, the benefits at this point would greatly outweigh > the costs of maintaining the old project structure. The old cordova-common > code in Cordova-Android 5.0.x would allow for plugins in the short term to > work with both projects until we get the new project structure ready. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13054) Write blog post on how to transition from file-transfer to XHR2
[ https://issues.apache.org/jira/browse/CB-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208565#comment-16208565 ] ASF GitHub Bot commented on CB-13054: - Github user macdonst commented on the issue: https://github.com/apache/cordova-docs/pull/746 @filmaj sorry, this got buried last week while I was away. The blog post looks great. I'd say release it. > Write blog post on how to transition from file-transfer to XHR2 > --- > > Key: CB-13054 > URL: https://issues.apache.org/jira/browse/CB-13054 > Project: Apache Cordova > Issue Type: Sub-task > Components: cordova-plugin-file-transfer >Reporter: Filip Maj >Assignee: Filip Maj > Labels: plugins-next > > Based on XHR2 research (see linked-to JIRA issue), write up a blog post! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11244) Update Android Project Structure to be more compatible with Android Studio
[ https://issues.apache.org/jira/browse/CB-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208559#comment-16208559 ] ASF subversion and git services commented on CB-11244: -- Commit 8b6430960e8aa6f1ef51e3ad218b11b773f89b1a in cordova-common's branch refs/heads/master from [~bowserj] [ https://git-wip-us.apache.org/repos/asf?p=cordova-common.git;h=8b64309 ] CB-11244: Spot fix for cordova-android PR #389 > Update Android Project Structure to be more compatible with Android Studio > -- > > Key: CB-11244 > URL: https://issues.apache.org/jira/browse/CB-11244 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: CordovaAndroidSix, android-next > > Currently our existing Android projects have the old Android Project > structure created by default, even for new projects, which makes no sense > since we no longer support Eclipse as the default project editor and have > moved to Android Studio for Android development. > The main reason for doing this is to clean up dependencies and to allow for > projects and dependencies to work more like how modern Android projects work > and to remove as much custom Gradle code as possible. This would also allow > us in the future to move towards having Android Plugin code work as Android > Libraries with Resources instead of just copying things across, which gives > us the ability to add JUnit tests and bundled resources. This would > dramatically increase the quality of plugins such as InAppBrowser, and third > party plugins such as the Barcode Scanner. > This would have to be done on the next major version, and the upgrade would > be tricky to do. However, the benefits at this point would greatly outweigh > the costs of maintaining the old project structure. The old cordova-common > code in Cordova-Android 5.0.x would allow for plugins in the short term to > work with both projects until we get the new project structure ready. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11244) Update Android Project Structure to be more compatible with Android Studio
[ https://issues.apache.org/jira/browse/CB-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208560#comment-16208560 ] ASF subversion and git services commented on CB-11244: -- Commit 0e71312d55ddcae2eaf6ecb40b2c3ffb653b8fc6 in cordova-common's branch refs/heads/master from [~bowserj] [ https://git-wip-us.apache.org/repos/asf?p=cordova-common.git;h=0e71312 ] CB-11244: eslint errors for spaces This closes #7 > Update Android Project Structure to be more compatible with Android Studio > -- > > Key: CB-11244 > URL: https://issues.apache.org/jira/browse/CB-11244 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: CordovaAndroidSix, android-next > > Currently our existing Android projects have the old Android Project > structure created by default, even for new projects, which makes no sense > since we no longer support Eclipse as the default project editor and have > moved to Android Studio for Android development. > The main reason for doing this is to clean up dependencies and to allow for > projects and dependencies to work more like how modern Android projects work > and to remove as much custom Gradle code as possible. This would also allow > us in the future to move towards having Android Plugin code work as Android > Libraries with Resources instead of just copying things across, which gives > us the ability to add JUnit tests and bundled resources. This would > dramatically increase the quality of plugins such as InAppBrowser, and third > party plugins such as the Barcode Scanner. > This would have to be done on the next major version, and the upgrade would > be tricky to do. However, the benefits at this point would greatly outweigh > the costs of maintaining the old project structure. The old cordova-common > code in Cordova-Android 5.0.x would allow for plugins in the short term to > work with both projects until we get the new project structure ready. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-13459) Rework headline hierarchy in /doc documents
[ https://issues.apache.org/jira/browse/CB-13459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Piotrowski (Sujan) reassigned CB-13459: --- Assignee: Jan Piotrowski (Sujan) > Rework headline hierarchy in /doc documents > --- > > Key: CB-13459 > URL: https://issues.apache.org/jira/browse/CB-13459 > Project: Apache Cordova > Issue Type: Sub-task > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) >Priority: Minor > > Now that the files are merged, headlines hierarchy can be reworked to start > with h1 for all documents. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13459) Rework headline hierarchy in /doc documents
Jan Piotrowski (Sujan) created CB-13459: --- Summary: Rework headline hierarchy in /doc documents Key: CB-13459 URL: https://issues.apache.org/jira/browse/CB-13459 Project: Apache Cordova Issue Type: Sub-task Components: cordova-docs Reporter: Jan Piotrowski (Sujan) Priority: Minor Now that the files are merged, headlines hierarchy can be reworked to start with h1 for all documents. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13349) Move "development" docs (install, Develop, Build, Deploy) to /doc
[ https://issues.apache.org/jira/browse/CB-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Piotrowski (Sujan) resolved CB-13349. - Resolution: Fixed merged > Move "development" docs (install, Develop, Build, Deploy) to /doc > - > > Key: CB-13349 > URL: https://issues.apache.org/jira/browse/CB-13349 > Project: Apache Cordova > Issue Type: Sub-task > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > When https://issues.apache.org/jira/browse/CB-1 is merged, there are > mainly lengthy development docs left on the main README that represent a very > special use case. > These could also be moved to individual files in /doc: > * installing-a-development-environemnt.md > * developing-the-website.md > * building-the-website.md > * deploying-the-website.md > These would of course be still linked in the README. Additionally some > crosslinks between the file would be added that match the natural flow one > would read them (install -> develop -> build -> deploy). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13055) remove --nofetch option and all old fetching code
[ https://issues.apache.org/jira/browse/CB-13055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Audrey So updated CB-13055: --- Description: Cordova uses cordova-fetch for fetching modules by default now. In the next major version, lets drop the older methods. This is great for reducing maintenance in cordova. Original fetch proposal is at https://github.com/cordova/cordova-discuss/pull/33 remove --nofetch option remove lazy_load remove gitclone.js remove npm dependency remove remoteload.js update anywhere that these files are used Proposal: https://github.com/apache/cordova-discuss/pull/76 was: Cordova uses cordova-fetch for fetching modules by default now. In the next major version, lets drop the older methods. This is great for reducing maintenance in cordova. Original fetch proposal is at https://github.com/cordova/cordova-discuss/pull/33 remove --nofetch option remove lazy_load remove gitclone.js remove npm dependency remove remoteload.js update anywhere that these files are used > remove --nofetch option and all old fetching code > - > > Key: CB-13055 > URL: https://issues.apache.org/jira/browse/CB-13055 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-lib >Reporter: Steve Gill > Labels: backlog, tools-next > Fix For: cordova@8 > > > Cordova uses cordova-fetch for fetching modules by default now. In the next > major version, lets drop the older methods. This is great for reducing > maintenance in cordova. Original fetch proposal is at > https://github.com/cordova/cordova-discuss/pull/33 > remove --nofetch option > remove lazy_load > remove gitclone.js > remove npm dependency > remove remoteload.js > update anywhere that these files are used > Proposal: https://github.com/apache/cordova-discuss/pull/76 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13417) Cordova-iOS Platform Release October 9, 2017
[ https://issues.apache.org/jira/browse/CB-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208255#comment-16208255 ] ASF GitHub Bot commented on CB-13417: - Github user audreyso commented on the issue: https://github.com/apache/cordova-docs/pull/750 Thanks! Has been merged! Please close @surajpindoria > Cordova-iOS Platform Release October 9, 2017 > > > Key: CB-13417 > URL: https://issues.apache.org/jira/browse/CB-13417 > Project: Apache Cordova > Issue Type: Task >Reporter: Suraj Pindoria >Assignee: Suraj Pindoria > > Following steps at > https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13458) Build issues while exporting and manual code signing even on cordova-ios 4.5.2
Dennis Patzer created CB-13458:
--
Summary: Build issues while exporting and manual code signing even
on cordova-ios 4.5.2
Key: CB-13458
URL: https://issues.apache.org/jira/browse/CB-13458
Project: Apache Cordova
Issue Type: Bug
Components: cordova-ios
Affects Versions: cordova-ios 4.5.0
Reporter: Dennis Patzer
Assignee: Suraj Pindoria
Priority: Blocker
After running cordova build ios with manual signing enabled in xcode 9, I get
the following error even after updating to cordova-ios 4.5.2 that should've
fixed this issue.
2017-10-17 21:42:50.890 xcodebuild[2005:19419] [MT] IDEDistribution:
-[IDEDistributionLogging
_createLoggingBundleAtPath:]: Created bundle at path
'/var/folders/0g/dd1ww3615ng7n2c4ryjjncbhgn/T/My
App_2017-10-17_21-42-50.889.xcdistributionlogs'.
2017-10-17 21:42:51.455 xcodebuild[2005:19419] [MT] IDEDistribution:
Step failed:
: Error
Domain=IDEDistributionSigningAssetStepErrorDomain
Code=0 "Locating signing assets failed."
UserInfo={NSLocalizedDescription=Locating signing assets failed.,
IDEDistributionSigningAssetStepUnderlyingErrors=(
"Error Domain=IDEProvisioningErrorDomain Code=9 \"\"My App.app\"
requires a provisioning profile
with the Push Notifications feature.\"
UserInfo={NSLocalizedDescription=\"My App.app\" requires a
provisioning profile with the Push Notifications feature.,
NSLocalizedRecoverySuggestion=Add a profile to the
\"provisioningProfiles\" dictionary in your Export Options property
list.}"
)}
error: exportArchive: "My App.app" requires a provisioning profile with
the Push Notifications feature.
Error Domain=IDEProvisioningErrorDomain Code=9 ""My App.app" requires a
provisioning profile with the
Push Notifications feature." UserInfo={NSLocalizedDescription="My
App.app" requires a provisioning
profile with the Push Notifications feature.,
NSLocalizedRecoverySuggestion=Add a profile to the
"provisioningProfiles" dictionary in your Export Options property list.}
** EXPORT FAILED **
Error: Error code 70 for command: xcodebuild with args:
-exportArchive,-archivePath,My
App.xcarchive,-exportOptionsPlist,/Users/myuser/customers/acme/my_app/app/platforms/ios/exportOptions.plist,-exportPath,/Users/myuser/customers/acme/my_app/app/platforms/ios/build/device
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13457) cordova build ios --release --device fails for packageType 'app-store'
[
https://issues.apache.org/jira/browse/CB-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Schauerte updated CB-13457:
-
Description:
build.json:
"release": {
"codeSignIdentity": "iPhone Distribution",
"developmentTeam": "OUR-TEAM-ID",
"packageType": "app-store",
"provisioningProfile": "VALID NAME OF A PROV-PROFILE",
"buildFlag": [
"EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
"ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
"LD_RUNPATH_SEARCH_PATHS = \"@executable_path/Frameworks\""
]
}
When using packageType=enterprise and a corresponding provisioningProfile the
release is finished successfully as expected, but with packageType=app-store we
receive the following messages:
[cordova] Entitlements:
[cordova]
[cordova] {
[cordova] "application-identifier" = "OUR-TEAM-ID.BUNDLE-ID";
[cordova] "beta-reports-active" = 1;
[cordova] "com.apple.developer.team-identifier" = OUR-TEAM-ID;
[cordova] "get-task-allow" = 0;
[cordova] }
[cordova]
[cordova]
[cordova] builtin-productPackagingUtility -entitlements -format xml -o
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/IntermediateBuildFilesPath/FINSTRAL.build/Release-iphoneos/FINSTRAL.build/FINSTRAL.app.xcent
[cordova]
[cordova] CodeSign
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova] cd
/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios
[cordova] export
CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
[cordova] export
PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/Users/schauerte/shared/ant-1.9.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin"
[cordova]
[cordova] Signing Identity: "iPhone Distribution: FINSTRAL SPA
(OUR-TEAM-ID)"
[cordova] Provisioning Profile: "FINSTRAL (AppStore)"
[cordova] (PROV-PROFILE-UID)
[cordova]
[cordova] /usr/bin/codesign --force --sign
70F84903046CDD6B734A987E4CB044FE5E18C5EA --entitlements
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/IntermediateBuildFilesPath/FINSTRAL.build/Release-iphoneos/FINSTRAL.build/FINSTRAL.app.xcent
--timestamp=none
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova]
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app:
unknown error -1=
[cordova] Command /usr/bin/codesign failed with exit code 1
[cordova]
[cordova] ** ARCHIVE FAILED **
[cordova]
[cordova]
[cordova] The following build commands failed:
[cordova] CodeSign
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova] (1 failure)
[cordova] Error: Error code 65 for command: xcodebuild with args:
-xcconfig,/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/cordova/build-release.xcconfig,-workspace,FINSTRAL.xcworkspace,-scheme,FINSTRAL,-configuration,Release,-destination,generic/platform=iOS,-archivePath,FINSTRAL.xcarchive,archive,CONFIGURATION_BUILD_DIR=/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/build/sharedpch,EMBEDDED_CONTENT_CONTAINS_SWIFT
= YES,ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO,LD_RUNPATH_SEARCH_PATHS =
"@executable_path/Frameworks"
This happens during Archiving and before Exporting.
As the messages say, the PROV-PROFILE etc. are resolved correctly. All
certificates are locally available in the login keychain. All profiles are
downloaded by xcode 9.
there are no outdated/old certificates or profiles on the mac system. we
deleted even old private keys.
We tried the same setup with different TEAM-IDS (and their corresponding
PROV-PROFILES). The error always occurrs.
We unlock the keycha
[jira] [Closed] (CB-13259) Crash on Samsung devices with android 6+
[
https://issues.apache.org/jira/browse/CB-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser closed CB-13259.
---
Resolution: Duplicate
Duplicate of CB-12754
> Crash on Samsung devices with android 6+
>
>
> Key: CB-13259
> URL: https://issues.apache.org/jira/browse/CB-13259
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-inappbrowser
>Affects Versions: cordova@7.0.0
> Environment: InAppBrowser 1.7.1
> OS: Android 6 and 7
> Samsung and Huawei devices
>Reporter: Veniamin Craciun
>
> Using latest version of cordova and InAppBrowser a crash occurs on Samsung
> and Huawei devices that run Android 6 or 7.
> Below is a google crash report from such device:
> {color:red}java.lang.IllegalArgumentException:
> at android.view.WindowManagerGlobal.findViewLocked
> (WindowManagerGlobal.java:473)
> at android.view.WindowManagerGlobal.removeView
> (WindowManagerGlobal.java:382)
> at android.view.WindowManagerImpl.removeViewImmediate
> (WindowManagerImpl.java:128)
> at android.app.Dialog.dismissDialog (Dialog.java:610)
> at android.app.Dialog.dismiss (Dialog.java:593)
> at org.apache.cordova.inappbrowser.InAppBrowser$5$1.onPageFinished
> (InAppBrowser.java:434)
> at com.android.webview.chromium.WebViewContentsClientAdapter.onPageFinished
> (WebViewContentsClientAdapter.java:196)
> at
> org.chromium.android_webview.AwContentsClientCallbackHelper$MyHandler.handleMessage
> (AwContentsClientCallbackHelper.java:65)
> at android.os.Handler.dispatchMessage (Handler.java:102)
> at android.os.Looper.loop (Looper.java:154)
> at android.app.ActivityThread.main (ActivityThread.java:6682)
> at java.lang.reflect.Method.invoke (Native Method)
> at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run
> (ZygoteInit.java:1520)
> at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1410){color}
> I already searched such crash and I couldn't find any report of this for
> cordova or inappbrowser. The problem seems to be occuring
> [here|https://github.com/apache/cordova-plugin-inappbrowser/blob/master/src/android/InAppBrowser.java#L434]
> that's because on samsung device it's needed to verify if dialog.isShowing()
> as stated from a StackOverflow
> [answer|https://stackoverflow.com/a/19511069/6723787]. That being said I
> think the bug can be easily solved by changing one line. I also want to
> mention that app only crashes if user has enabled "Don't keep activities" on
> Settings->Developer Options.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13457) cordova build ios --release --device fails for packageType 'app-store'
[
https://issues.apache.org/jira/browse/CB-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Schauerte updated CB-13457:
-
Description:
build.json:
"release": {
"codeSignIdentity": "iPhone Distribution",
"developmentTeam": "OUR-TEAM-ID",
"packageType": "app-store",
"provisioningProfile": "VALID NAME OF A PROV-PROFILE",
"buildFlag": [
"EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
"ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
"LD_RUNPATH_SEARCH_PATHS = \"@executable_path/Frameworks\""
]
}
When using packageType=enterprise and a corresponding provisioningProfile the
release is finished successfully as expected, but with packageType=app-store we
receive the following messages:
[cordova] Entitlements:
[cordova]
[cordova] {
[cordova] "application-identifier" = "OUR-TEAM-ID.BUNDLE-ID";
[cordova] "beta-reports-active" = 1;
[cordova] "com.apple.developer.team-identifier" = OUR-TEAM-ID;
[cordova] "get-task-allow" = 0;
[cordova] }
[cordova]
[cordova]
[cordova] builtin-productPackagingUtility -entitlements -format xml -o
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/IntermediateBuildFilesPath/FINSTRAL.build/Release-iphoneos/FINSTRAL.build/FINSTRAL.app.xcent
[cordova]
[cordova] CodeSign
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova] cd
/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios
[cordova] export
CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
[cordova] export
PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/Users/schauerte/shared/ant-1.9.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin"
[cordova]
[cordova] Signing Identity: "iPhone Distribution: FINSTRAL SPA
(OUR-TEAM-ID)"
[cordova] Provisioning Profile: "FINSTRAL (AppStore)"
[cordova] (PROV-PROFILE-UID)
[cordova]
[cordova] /usr/bin/codesign --force --sign
70F84903046CDD6B734A987E4CB044FE5E18C5EA --entitlements
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/IntermediateBuildFilesPath/FINSTRAL.build/Release-iphoneos/FINSTRAL.build/FINSTRAL.app.xcent
--timestamp=none
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova]
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app:
unknown error -1=
[cordova] Command /usr/bin/codesign failed with exit code 1
[cordova]
[cordova] ** ARCHIVE FAILED **
[cordova]
[cordova]
[cordova] The following build commands failed:
[cordova] CodeSign
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova] (1 failure)
[cordova] Error: Error code 65 for command: xcodebuild with args:
-xcconfig,/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/cordova/build-release.xcconfig,-workspace,FINSTRAL.xcworkspace,-scheme,FINSTRAL,-configuration,Release,-destination,generic/platform=iOS,-archivePath,FINSTRAL.xcarchive,archive,CONFIGURATION_BUILD_DIR=/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/build/sharedpch,EMBEDDED_CONTENT_CONTAINS_SWIFT
= YES,ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO,LD_RUNPATH_SEARCH_PATHS =
"@executable_path/Frameworks"
This happens during Archiving and before Exporting.
As the messages say, the PROV-PROFILE etc. are resolved correctly. All
certificates are locally available in the login keychain. All profiles are
downloaded by xcode 9.
there are no outdated/old certificates or profiles on the mac system. we
deleted even old private keys.
We tried the same setup with different TEAM-IDS (and their corresponding
PROV-PROFILES). The error always occurrs.
We unlock the keycha
[jira] [Updated] (CB-13381) In projects where window.console.log = console.log = null; console logging in cordova.js template file for android platform results in error such as Uncaught TypeError: con
[ https://issues.apache.org/jira/browse/CB-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13381: Component/s: (was: cordova-android) cordova-js > In projects where window.console.log = console.log = null; console logging in > cordova.js template file for android platform results in error such as > Uncaught TypeError: console.log is not a function > -- > > Key: CB-13381 > URL: https://issues.apache.org/jira/browse/CB-13381 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-js >Affects Versions: Master > Environment: cordova.js template for android platform >Reporter: Shubham Jha >Assignee: Joe Bowser >Priority: Minor > Labels: beginner, easyfix > Fix For: Master > > > In projects where window.console.log = console.log = null; console logging in > cordova.js template file for android platform cause Uncaught TypeError: > console.log is not a function -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13457) cordova build ios --release --device fails for packageType 'app-store'
Felix Schauerte created CB-13457:
Summary: cordova build ios --release --device fails for
packageType 'app-store'
Key: CB-13457
URL: https://issues.apache.org/jira/browse/CB-13457
Project: Apache Cordova
Issue Type: Bug
Components: cordova-ios
Environment: Mac OS Sierra (10.12.6)
Xcode 9
Cordova CLI 7.1.0
cordova-ios:
cordova-ios@4.5.2
or https://github.com/jrryhrtn/cordova-ios.git
or https://github.com/apache/cordova-ios.git
Reporter: Felix Schauerte
Assignee: Suraj Pindoria
build.json:
{{"release": {
"codeSignIdentity": "iPhone Distribution",
"developmentTeam": "OUR-TEAM-ID",
"packageType": "app-store",
"provisioningProfile": "VALID NAME OF A PROV-PROFILE",
"buildFlag": [
"EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
"ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
"LD_RUNPATH_SEARCH_PATHS = \"@executable_path/Frameworks\""
]
}
}}
When using packageType=enterprise and a corresponding provisioningProfile the
release is finished successfully as expected, but with packageType=app-store we
receive the following messages:
{{ [cordova] Entitlements:
[cordova]
[cordova] {
[cordova] "application-identifier" = "OUR-TEAM-ID.BUNDLE-ID";
[cordova] "beta-reports-active" = 1;
[cordova] "com.apple.developer.team-identifier" = OUR-TEAM-ID;
[cordova] "get-task-allow" = 0;
[cordova] }
[cordova]
[cordova]
[cordova] builtin-productPackagingUtility -entitlements -format xml -o
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/IntermediateBuildFilesPath/FINSTRAL.build/Release-iphoneos/FINSTRAL.build/FINSTRAL.app.xcent
[cordova]
[cordova] CodeSign
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova] cd
/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios
[cordova] export
CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
[cordova] export
PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/Users/schauerte/shared/ant-1.9.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin"
[cordova]
[cordova] Signing Identity: "iPhone Distribution: FINSTRAL SPA
(OUR-TEAM-ID)"
[cordova] Provisioning Profile: "FINSTRAL (AppStore)"
[cordova] (PROV-PROFILE-UID)
[cordova]
[cordova] /usr/bin/codesign --force --sign
70F84903046CDD6B734A987E4CB044FE5E18C5EA --entitlements
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/IntermediateBuildFilesPath/FINSTRAL.build/Release-iphoneos/FINSTRAL.build/FINSTRAL.app.xcent
--timestamp=none
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova]
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app:
unknown error -1=
[cordova] Command /usr/bin/codesign failed with exit code 1
[cordova]
[cordova] ** ARCHIVE FAILED **
[cordova]
[cordova]
[cordova] The following build commands failed:
[cordova] CodeSign
/Users/schauerte/Library/Developer/Xcode/DerivedData/FINSTRAL-bsnohhydgksblzfcqjeuvibucnhv/Build/Intermediates.noindex/ArchiveIntermediates/FINSTRAL/InstallationBuildProductsLocation/Applications/FINSTRAL.app
[cordova] (1 failure)
[cordova] Error: Error code 65 for command: xcodebuild with args:
-xcconfig,/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/cordova/build-release.xcconfig,-workspace,FINSTRAL.xcworkspace,-scheme,FINSTRAL,-configuration,Release,-destination,generic/platform=iOS,-archivePath,FINSTRAL.xcarchive,archive,CONFIGURATION_BUILD_DIR=/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/schauerte/tatakoto/dev/schauerte/cleverdox/build/fis.productive/local/ios/platforms/ios/build/sharedpch,EMBEDDED_CONTENT_CONTAINS_SWIFT
= YES,ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO,LD_RUNPATH_SEARCH_PATHS =
"@executable_path/Frameworks"}}
This happens during Ar
[jira] [Resolved] (CB-12802) Fix build.gradle to sign when building with multiple APK is enable.
[ https://issues.apache.org/jira/browse/CB-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-12802. - Resolution: Fixed > Fix build.gradle to sign when building with multiple APK is enable. > --- > > Key: CB-12802 > URL: https://issues.apache.org/jira/browse/CB-12802 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova@7.0.0 >Reporter: Kevin Lot > Labels: android-next > > When multiple APKs build is enable, you cannot sign and the build crashes. > Method for sign can be parameters of command or build.json, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13456) Cookies are lost if app closes within 30 seconds
Anton Bessonov created CB-13456: --- Summary: Cookies are lost if app closes within 30 seconds Key: CB-13456 URL: https://issues.apache.org/jira/browse/CB-13456 Project: Apache Cordova Issue Type: Bug Components: cordova-android Affects Versions: 6.1.0 Environment: # Android 4.4.4/Nexus 4/crosswalk 20 # Android 6/crosswalk 20 # Android 7/Galaxy S7/without crosswalk No problems on iOS10/iPhone6 with UiWebView. Reporter: Anton Bessonov Assignee: Joe Bowser On the first start after app installation, cookies are lost if app closes within 30 seconds after cookies set (login). Used cookie is HttpOnly and has expiration date. If I wait more than 30 seconds and then close the app, cookies are not deleted. localStorage is not emptied, just cookie. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13349) Move "development" docs (install, Develop, Build, Deploy) to /doc
[ https://issues.apache.org/jira/browse/CB-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208073#comment-16208073 ] ASF GitHub Bot commented on CB-13349: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-docs/pull/745 > Move "development" docs (install, Develop, Build, Deploy) to /doc > - > > Key: CB-13349 > URL: https://issues.apache.org/jira/browse/CB-13349 > Project: Apache Cordova > Issue Type: Sub-task > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > When https://issues.apache.org/jira/browse/CB-1 is merged, there are > mainly lengthy development docs left on the main README that represent a very > special use case. > These could also be moved to individual files in /doc: > * installing-a-development-environemnt.md > * developing-the-website.md > * building-the-website.md > * deploying-the-website.md > These would of course be still linked in the README. Additionally some > crosslinks between the file would be added that match the natural flow one > would read them (install -> develop -> build -> deploy). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13349) Move "development" docs (install, Develop, Build, Deploy) to /doc
[ https://issues.apache.org/jira/browse/CB-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208072#comment-16208072 ] ASF subversion and git services commented on CB-13349: -- Commit 246af51cffb8636b5764c7f005bb8ec683217847 in cordova-docs's branch refs/heads/master from Jan Piotrowski [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=246af51 ] CB-13349: Move "development" docs to /doc - Move "development" docs (install, Develop, Build, Deploy) to /doc - Add a bit of crosslinking This closes #745 > Move "development" docs (install, Develop, Build, Deploy) to /doc > - > > Key: CB-13349 > URL: https://issues.apache.org/jira/browse/CB-13349 > Project: Apache Cordova > Issue Type: Sub-task > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > When https://issues.apache.org/jira/browse/CB-1 is merged, there are > mainly lengthy development docs left on the main README that represent a very > special use case. > These could also be moved to individual files in /doc: > * installing-a-development-environemnt.md > * developing-the-website.md > * building-the-website.md > * deploying-the-website.md > These would of course be still linked in the README. Additionally some > crosslinks between the file would be added that match the natural flow one > would read them (install -> develop -> build -> deploy). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13417) Cordova-iOS Platform Release October 9, 2017
[ https://issues.apache.org/jira/browse/CB-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208067#comment-16208067 ] ASF subversion and git services commented on CB-13417: -- Commit 66921ad12ed554ea06d4602c77f3e5c79f1df9c4 in cordova-docs's branch refs/heads/master from [~surajpindoria] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=66921ad ] CB-13417: Blog post for cordova-ios@4.5.2 > Cordova-iOS Platform Release October 9, 2017 > > > Key: CB-13417 > URL: https://issues.apache.org/jira/browse/CB-13417 > Project: Apache Cordova > Issue Type: Task >Reporter: Suraj Pindoria >Assignee: Suraj Pindoria > > Following steps at > https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. https://developer.android.com/reference/android/webkit/WebSettings.html void setUseWideViewPort (boolean use) 'Sets whether the WebView should enable support for the "viewport" HTML meta tag or should use a wide viewport.' This should be set to true otherwise WebView will ignore the meta tag causing undesired effects on the application. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. https://developer.android.com/reference/android/webkit/WebSettings.html void setUseWideViewPort (boolean use) "Sets whether the WebView should enable support for the "viewport" HTML meta tag or should use a wide viewport." This should be set to true otherwise WebView will ignore the meta tag causing undesired effects on the application. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine.java > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewpor
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. https://developer.android.com/reference/android/webkit/WebSettings.html setUseWideViewPort void setUseWideViewPort (boolean use) "Sets whether the WebView should enable support for the "viewport" HTML meta tag or should use a wide viewport." This should be set to true otherwise WebView will ignore the meta tag causing undesired effects on the application. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. https://developer.android.com/reference/android/webkit/WebSettings.html setUseWideViewPort void setUseWideViewPort (boolean use) This should be set to true otherwise WebView will ignore the meta tag causing undesired effects on the application. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine.java > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prio
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. https://developer.android.com/reference/android/webkit/WebSettings.html void setUseWideViewPort (boolean use) "Sets whether the WebView should enable support for the "viewport" HTML meta tag or should use a wide viewport." This should be set to true otherwise WebView will ignore the meta tag causing undesired effects on the application. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. https://developer.android.com/reference/android/webkit/WebSettings.html setUseWideViewPort void setUseWideViewPort (boolean use) "Sets whether the WebView should enable support for the "viewport" HTML meta tag or should use a wide viewport." This should be set to true otherwise WebView will ignore the meta tag causing undesired effects on the application. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine.java > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be movea
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. https://developer.android.com/reference/android/webkit/WebSettings.html setUseWideViewPort void setUseWideViewPort (boolean use) This should be set to true otherwise WebView will ignore the meta tag causing undesired effects on the application. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. >From my understanding, settings.setUseWideViewPort(true) must be set to true >otherwise WebView will ignore the meta tag. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine.java > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > https://developer.android.com/reference/android/webkit/WebSettings.html > setUseWideViewPort > void setUseWideViewPort (boolean use) > This should be set to true otherwise WebView will ign
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. >From my understanding, settings.setUseWideViewPort(true) must be set to true >otherwise WebView will ignore the meta tag. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. >From my understanding, webView.getSettings().setUseWideViewPort(true) must be >set to true otherwise WebView will ignore the meta tag. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine.java > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > From my understanding, settings.setUseWideViewPort(true) must be set to true > otherwise WebView will ignore the meta tag. > Thanks! > Related: > https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 > https://fetch-info.blogspot.com/2015/06/include-viewport-
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine.java Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. >From my understanding, webView.getSettings().setUseWideViewPort(true) must be >set to true otherwise WebView will ignore the meta tag. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. >From my understanding, webView.getSettings().setUseWideViewPort(true) must be >set to true otherwise WebView will ignore the meta tag. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine.java > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > From my understanding, webView.getSettings().setUseWideViewPort(true) must be > set to true otherwise WebView will ignore the meta tag. > Thanks! > Related: > https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 > https://fetch-info.blogspot.com/2015
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. >From my understanding, webView.getSettings().setUseWideViewPort(true) must be >set to true otherwise WebView will ignore the meta tag. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. >From my understanding, webView.getSettings().setUseWideViewPort(true) must be >set to true otherwise WebView will ignore the meta tag. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > From my understanding, webView.getSettings().setUseWideViewPort(true) must be > set to true otherwise WebView will ignore the meta tag. > Thanks! > Related: > https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 > https://fetch-info.blogspot.com/2015/06/include
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. >From my understanding, webView.getSettings().setUseWideViewPort(true) must be >set to true otherwise WebView will ignore the meta tag. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > From my understanding, webView.getSettings().setUseWideViewPort(true) must be > set to true otherwise WebView will ignore the meta tag. > Thanks! > Related: > https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 > https://fetch-info.blogspot.com/2015/06/include-viewport-settings-in-cordova-if.html > https://stackoverflow.com/questions/22161421/viewport-meta-tag-ignored-in-android-4-4-webview -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! Related: https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > Thanks! > Related: > https://stackoverflow.com/questions/44923541/setting-viewport-width-is-ignored-on-cordova-7 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. > This has been observed in a Motorolla X 37 and Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile Safari/537.36 The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. This has been observed in a Motorolla X 37 and > Samsung Galaxy S7. > Mozilla/5.0 (Linux; Android 6.0; XT1095 Build/MPES24.49-18-7) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.98 Mobile > Safari/537.36 > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. This has been observed in a Motorolla X 37 and > Samsung Galaxy S7. > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13454) Icon 40x40@2x is not copied
[
https://issues.apache.org/jira/browse/CB-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207862#comment-16207862
]
Suraj Pindoria commented on CB-13454:
-
Thanks for reporting this! I meant to just rearrange the icon list to make it
more readable and accidentally forgot to add that one back in.
> Icon 40x40@2x is not copied
> ---
>
> Key: CB-13454
> URL: https://issues.apache.org/jira/browse/CB-13454
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Affects Versions: cordova-ios 4.5.0
>Reporter: Thomas Brian
>Assignee: Suraj Pindoria
>
> Hi,
> The 40...@2x.png icon (80x80) is no longer copied in cordova-ios 4.5.2.
> This is a regression from version 4.5.1.
> The commit that introduced the bug is this one
> https://github.com/apache/cordova-ios/pull/341/commits/7b7964f349276ac3f3452e2dad817dfdadca29b3
>
> The file names in prepare.js were re-ordered but the line {dest:
> 'icon...@2x.png', width: 80, height: 80} got deleted by mistake.
> Have a nice day,
> Thomas
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12939) CB-12015 Causes text to not render on Android 4.4.4
[ https://issues.apache.org/jira/browse/CB-12939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207843#comment-16207843 ] Tyler Vorpahl commented on CB-12939: [~bowserj] reverting CB-12015 causes the issue with Android viewport to return where the app can be moved inside the window. I've opened up a ticket CB-13455. > CB-12015 Causes text to not render on Android 4.4.4 > --- > > Key: CB-12939 > URL: https://issues.apache.org/jira/browse/CB-12939 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: cordova@7.0.0 > Environment: Android 4.4.4 on Nexus 7 (2013) > cordova@7.0.1 > cordova-android@6.2.3 > Windows 10 15063.413 >Reporter: Adam Venezia >Assignee: Joe Bowser >Priority: Minor > > I've been able to nail this down in my app, but not in a bare reproduceable > app, unfortunately, but I know exactly what to comment out to make the issue > go away. > My Cordova app uses a custom font (woff or ttf exhibited this), declared in > my CSS file, and applied to the body tag so all text uses it. When the app > launches, several text fields do not render, the text is invisible. Rotating > the device causes the text to reappear. Attaching to Chrome debug tools > causes it to reappear. Not using the custom font, such as defaulting to > Arial, the text appeared just fine. > Android 5.x, 6.x, and 7.x don't appear affected; even worse, the Visual > Studio Android Emulator for 4.4 (x86) does not exhibit the issue, nor does > the Google Emulator for 4.4 (ARM) exhibit the issue. I did a hard reset of my > Nexus 7 on 4.4.4 and the issue still arose. > I started using older versions of cordova-android, and started with 6.0.0. > 6.0.0 = worked > 6.1.2 = worked > 6.2.0 = worked > 6.2.1 = worked > 6.2.2 = worked > 6.2.3 = broken > Comparing 6.2.2 with 6.2.3, I discovered this code in SystemWebViewEngine.java > // Enable scaling > // Fix for CB-12015 > settings.setUseWideViewPort(true); > settings.setLoadWithOverviewMode(true); > Viewing the bug entry here on Jira, seems like that does fix some people > having a different issue with viewport scaling. However, when I comment out > those 2 lines of code, my issue goes away. That makes things a little sticky. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13455) Reverting CB-12015 causes viewport issues on Android
[ https://issues.apache.org/jira/browse/CB-13455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Vorpahl updated CB-13455: --- Description: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. The defect causes the screen to be moveable within the viewport, allowing the user to pan the page around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! was: CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. The defect causes the app the be moveable within the viewport, allowing the user to slide the screen around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! > Reverting CB-12015 causes viewport issues on Android > > > Key: CB-13455 > URL: https://issues.apache.org/jira/browse/CB-13455 > Project: Apache Cordova > Issue Type: Bug > Environment: > > > > > > > > > > > > > /> > src="../images/android/ldpi/splash_land.png" /> > src="../images/android/mdpi/splash_land.png" /> > src="../images/android/hdpi/splash_land.png" /> > src="../images/android/xhdpi/splash_land.png" /> > src="../images/android/xxhdpi/splash_land.png" /> > src="../images/android/ldpi/splash_port.png" /> > src="../images/android/mdpi/splash_port.png" /> > src="../images/android/hdpi/splash_port.png" /> > src="../images/android/xhdpi/splash_port.png" /> > src="../images/android/xxhdpi/splash_port.png" /> > > >Reporter: Tyler Vorpahl >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > CB-12015 added the following two lines: > # settings.setUseWideViewPort(true); > # settings.setLoadWithOverviewMode(true); > To initWebViewSettings() method in SystemWebViewEngine > Using the following viewport tags in our index.html of our application, we > have not had any issues with Android. > > Since CB-12939, reverting the change in CB-12015 has caused our app to not > properly fit the viewport. This has been observed in a Motorolla X 37 and > Samsung Galaxy S7. > The defect causes the screen to be moveable within the viewport, allowing the > user to pan the page around where this was not observed prior to CB-12015 > being reverted as a result of CB-12939. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13455) Reverting CB-12015 causes viewport issues on Android
Tyler Vorpahl created CB-13455: -- Summary: Reverting CB-12015 causes viewport issues on Android Key: CB-13455 URL: https://issues.apache.org/jira/browse/CB-13455 Project: Apache Cordova Issue Type: Bug Environment: Reporter: Tyler Vorpahl Priority: Minor CB-12015 added the following two lines: # settings.setUseWideViewPort(true); # settings.setLoadWithOverviewMode(true); To initWebViewSettings() method in SystemWebViewEngine Using the following viewport tags in our index.html of our application, we have not had any issues with Android. Since CB-12939, reverting the change in CB-12015 has caused our app to not properly fit the viewport. This has been observed in a Motorolla X 37 and Samsung Galaxy S7. The defect causes the app the be moveable within the viewport, allowing the user to slide the screen around where this was not observed prior to CB-12015 being reverted as a result of CB-12939. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13454) Icon 40x40@2x is not copied
Thomas Brian created CB-13454:
-
Summary: Icon 40x40@2x is not copied
Key: CB-13454
URL: https://issues.apache.org/jira/browse/CB-13454
Project: Apache Cordova
Issue Type: Bug
Components: cordova-ios
Affects Versions: cordova-ios 4.5.0
Reporter: Thomas Brian
Assignee: Suraj Pindoria
Hi,
The 40...@2x.png icon (80x80) is no longer copied in cordova-ios 4.5.2.
This is a regression from version 4.5.1.
The commit that introduced the bug is this one
https://github.com/apache/cordova-ios/pull/341/commits/7b7964f349276ac3f3452e2dad817dfdadca29b3
The file names in prepare.js were re-ordered but the line {dest:
'icon...@2x.png', width: 80, height: 80} got deleted by mistake.
Have a nice day,
Thomas
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13440) Improve "Using Flags" for iOS
[ https://issues.apache.org/jira/browse/CB-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207725#comment-16207725 ] ASF GitHub Bot commented on CB-13440: - Github user janpio commented on the issue: https://github.com/apache/cordova-docs/pull/748 (And now me being an idiot I even deleted the forked repo so I can't update the PR... will have to create a new one when I understood what is actually going on) > Improve "Using Flags" for iOS > - > > Key: CB-13440 > URL: https://issues.apache.org/jira/browse/CB-13440 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Table could use some improvement: > - Formatting of descriptions > - Order of lines -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13424) [cordova-osx] Not adding plugins to the osx platform
[
https://issues.apache.org/jira/browse/CB-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207506#comment-16207506
]
ASF GitHub Bot commented on CB-13424:
-
Github user JoseExposito commented on the issue:
https://github.com/apache/cordova-osx/pull/43
Thanks for reviewing @giuseppelt, changed
> [cordova-osx] Not adding plugins to the osx platform
>
>
> Key: CB-13424
> URL: https://issues.apache.org/jira/browse/CB-13424
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-osx
>Reporter: José Expósito
>Assignee: Tobias Bocanegra
>Priority: Blocker
>
> cordova plugin add does not work on macOS.
> It is necessary to open "platforms/osx/HelloCordova.xcodeproj" and manually
> add the plugin to "platforms/osx/HelloCordova/config.xml":
> {code}
>
> xmlns="http://www.w3.org/ns/widgets";
> xmlns:cdv="http://cordova.apache.org/ns/1.0";>
> [...]
>
>
>
> [...]
>
> {code}
> I noticed this happens with Cordova core plugins with official macOS support
> like cordova-plugin-device or cordova-plugin-file.
> Also experimented while migrating cordova-plugin-camera:
> https://github.com/apache/cordova-plugin-camera/pull/290
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13424) [cordova-osx] Not adding plugins to the osx platform
[
https://issues.apache.org/jira/browse/CB-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207501#comment-16207501
]
ASF GitHub Bot commented on CB-13424:
-
Github user giuseppelt commented on a diff in the pull request:
https://github.com/apache/cordova-osx/pull/43#discussion_r145098266
--- Diff: bin/templates/scripts/cordova/Api.js ---
@@ -199,8 +201,8 @@ Api.prototype.addPlugin = function (plugin,
installOptions) {
* CordovaError instance.
*/
Api.prototype.removePlugin = function (plugin, uninstallOptions) {
-var Plugman = require('./lib/plugman/Plugman');
-return Plugman.get(this.locations, this.events).removePlugin(plugin,
uninstallOptions);
+var xcodeproj = projectFile.parse(this.locations);
+return PluginManager.get(self.platform, self.locations,
xcodeproj).removePlugin(plugin, uninstallOptions)
--- End diff --
`self` is undefined here
replace with `this`
> [cordova-osx] Not adding plugins to the osx platform
>
>
> Key: CB-13424
> URL: https://issues.apache.org/jira/browse/CB-13424
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-osx
>Reporter: José Expósito
>Assignee: Tobias Bocanegra
>Priority: Blocker
>
> cordova plugin add does not work on macOS.
> It is necessary to open "platforms/osx/HelloCordova.xcodeproj" and manually
> add the plugin to "platforms/osx/HelloCordova/config.xml":
> {code}
>
> xmlns="http://www.w3.org/ns/widgets";
> xmlns:cdv="http://cordova.apache.org/ns/1.0";>
> [...]
>
>
>
> [...]
>
> {code}
> I noticed this happens with Cordova core plugins with official macOS support
> like cordova-plugin-device or cordova-plugin-file.
> Also experimented while migrating cordova-plugin-camera:
> https://github.com/apache/cordova-plugin-camera/pull/290
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12366) InAppBrowser overlaps iOS status bar
[
https://issues.apache.org/jira/browse/CB-12366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207225#comment-16207225
]
ASF GitHub Bot commented on CB-12366:
-
Github user jcesarmobile commented on the issue:
https://github.com/apache/cordova-plugin-inappbrowser/pull/209
@CVeniamin create an issue on issues.cordova.io if you haven't done it yet.
> InAppBrowser overlaps iOS status bar
>
>
> Key: CB-12366
> URL: https://issues.apache.org/jira/browse/CB-12366
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-inappbrowser
> Environment: iOS
>Reporter: Reid Beels
>Assignee: Shazron Abdullah
>
> This affects the unreleased 1.6.2-dev (which I can't select from the affects
> version field).
> Since the change introduced in CB-11136 /
> https://github.com/apache/cordova-plugin-inappbrowser/pull/187, the IAB
> window seems to be rendering on top of the iOS status bar.
> Dropping the {{tmpWindow}} window level from {{UIWindowLevelAlert}} to
> {{UIWindowLevelNormal}} seems to fix the issue, but I'm not sure how this
> affects the problem CB-11136 set out to solve.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
