[jira] [Commented] (CB-11905) Error message when adding IAB to iOS project
[
https://issues.apache.org/jira/browse/CB-11905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526857#comment-15526857
]
Steve Husting commented on CB-11905:
Tried:
1) Removed platforms, then added.
2) Removed plugins, then added.
3) Made new project and added IAB plugin, moved that IAB folder in /plugins to
the problem project’s /plugins and it built iOS with the following errors on
cordova build ios (ellipses added manually):
2016-09-27 10:15:58.885 xcodebuild[69912:748615]
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in
dictionary on line 39. Parsing will be abandoned. Break on
_CFPropertyListMissingSemicolon to debug.
2016-09-27 10:15:58.886 xcodebuild[69912:748615]
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in
dictionary on line 39. Parsing will be abandoned. Break on
_CFPropertyListMissingSemicolon to debug.
2016-09-27 10:15:58.886 xcodebuild[69912:748615] Error
Domain=NSCocoaErrorDomain Code=3840 "Unexpected character / at line 1"
UserInfo={NSDebugDescription=Unexpected character / at line 1,
kCFPropertyListOldStyleParsingError=Error Domain=NSCocoaErrorDomain Code=3840
"Missing ';' on line 39" UserInfo={NSDebugDescription=Missing ';' on line 39}}
xcodebuild: error: Unable to read project ' Essentials".xcodeproj'.
Reason: Project
/Users/.../.../APPS/..._Essentials/...Essentials/platforms/ios/...
Essentials".xcodeproj cannot be opened because the project file cannot be
parsed.
> Error message when adding IAB to iOS project
>
>
> Key: CB-11905
> URL: https://issues.apache.org/jira/browse/CB-11905
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, iOS, Plugin InAppBrowser
>Affects Versions: 1.4.0
> Environment: OS X El Capitan 10.11.6, ios 4.2.1
>Reporter: Steve Husting
> Fix For: 1.4.0
>
>
> When I ran cordova platform add ios on a new project for the first time, I
> got the error:
> iOS project created with cordova-ios@4.2.1
> Installing "cordova-plugin-inappbrowser" for ios
> Failed to install 'cordova-plugin-inappbrowser':undefined
> Error: Expected "/*" or ";" but "/" found.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11905) Error message when adding IAB to iOS project
Steve Husting created CB-11905: -- Summary: Error message when adding IAB to iOS project Key: CB-11905 URL: https://issues.apache.org/jira/browse/CB-11905 Project: Apache Cordova Issue Type: Bug Components: CLI, iOS, Plugin InAppBrowser Affects Versions: 1.4.0 Environment: OS X El Capitan 10.11.6, ios 4.2.1 Reporter: Steve Husting Fix For: 1.4.0 When I ran cordova platform add ios on a new project for the first time, I got the error: iOS project created with cordova-ios@4.2.1 Installing "cordova-plugin-inappbrowser" for ios Failed to install 'cordova-plugin-inappbrowser':undefined Error: Expected "/*" or ";" but "/" found. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11013) IAB enabling background play of YouTube videos?
[ https://issues.apache.org/jira/browse/CB-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426926#comment-15426926 ] Steve Husting commented on CB-11013: My issue is resolved! Hurray! Regards, Steve Husting, Webmaster Email: shust...@aeteam.net Team Associated > IAB enabling background play of YouTube videos? > --- > > Key: CB-11013 > URL: https://issues.apache.org/jira/browse/CB-11013 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 3.5.0 > Environment: android OS >Reporter: Steve Husting >Assignee: Sergey Shakhnazarov > Labels: Android, triaged > > Google Play send me an email, saying, "Make sure your app doesn’t access or > use a service or API in a manner that violates its terms of service, for > example, by enabling background play of YouTube videos." My app uses IAB > extensively to play videos from YouTube. In some way it is violating the > terms of service by playing the videos through IAB. Please examine and fix > this bug so it no longer violates the rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11013) IAB enabling background play of YouTube videos?
[ https://issues.apache.org/jira/browse/CB-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228343#comment-15228343 ] Steve Husting commented on CB-11013: Is there JS I can attach to the IAB so it will shut down the YouTube video safely? > IAB enabling background play of YouTube videos? > --- > > Key: CB-11013 > URL: https://issues.apache.org/jira/browse/CB-11013 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 3.5.0 > Environment: android OS >Reporter: Steve Husting > Labels: Android, wfc > > Google Play send me an email, saying, "Make sure your app doesn’t access or > use a service or API in a manner that violates its terms of service, for > example, by enabling background play of YouTube videos." My app uses IAB > extensively to play videos from YouTube. In some way it is violating the > terms of service by playing the videos through IAB. Please examine and fix > this bug so it no longer violates the rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11013) IAB enabling background play of YouTube videos?
Steve Husting created CB-11013: -- Summary: IAB enabling background play of YouTube videos? Key: CB-11013 URL: https://issues.apache.org/jira/browse/CB-11013 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.5.0 Environment: android OS Reporter: Steve Husting Google Play send me an email, saying, "Make sure your app doesn’t access or use a service or API in a manner that violates its terms of service, for example, by enabling background play of YouTube videos." My app uses IAB extensively to play videos from YouTube. In some way it is violating the terms of service by playing the videos through IAB. Please examine and fix this bug so it no longer violates the rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-8914) In Xcode, "HelloCordova" appears as the app name, even though the app name was changed in config.xml
Steve Husting created CB-8914: - Summary: In Xcode, "HelloCordova" appears as the app name, even though the app name was changed in config.xml Key: CB-8914 URL: https://issues.apache.org/jira/browse/CB-8914 Project: Apache Cordova Issue Type: Bug Components: CLI, iOS Environment: Mac OS X Yosemite 10.10.3 on MacBook Pro (pre-Retina). cordova -v = 5.0.0. Making iOS version of app. Xcode 6.2. Reporter: Steve Husting After changing config.xml to "Calligraphy," doing cordova prepare ios, and clicking on the app's Calligraphy.xcodeproj file in platforms/ios, Xcode opens up and shows the HelloCordova app name at upper left. Xcode's Product > Clean does not change it. However, the correct name appears under PROJECT and TARGETS. The correct name also appears in /platform/ios/Calligraphy/config.xml. So where is Xcode drawing HelloCordova from? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8911) cordova prepare ios complains of "Error: Unexpected close tag" for ""
[ https://issues.apache.org/jira/browse/CB-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Husting closed CB-8911. - Resolution: Fixed Coder error, not Cordova error. > cordova prepare ios complains of "Error: Unexpected close tag" for > "" > --- > > Key: CB-8911 > URL: https://issues.apache.org/jira/browse/CB-8911 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, iOS >Affects Versions: 3.5.0 > Environment: Mac OS X Yosemite 10.10.3. cordova -v = 5.0.0. Making > iOS version of app. MacBook Pro (pre-Retina version). >Reporter: Steve Husting > Fix For: Master > > > After adding inAppBrowser to config.xml as > > > > then running cordova prepare ios, get error in CLI: > Parsing /Users/dragonhu/Documents/PhoneGap_apps/gothic2015/config.xml failed > Error: Unexpected close tag > Line: 28 > Column: 9 > Char: > > ... that is the end > of -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8911) cordova prepare ios complains of "Error: Unexpected close tag" for ""
[ https://issues.apache.org/jira/browse/CB-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512747#comment-14512747 ] Steve Husting commented on CB-8911: --- My bad. The error pointed to the wrong line. The error was on a line much earlier and the code had > instead of <. This was fixed and all went well. > cordova prepare ios complains of "Error: Unexpected close tag" for > "" > --- > > Key: CB-8911 > URL: https://issues.apache.org/jira/browse/CB-8911 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, iOS >Affects Versions: 3.5.0 > Environment: Mac OS X Yosemite 10.10.3. cordova -v = 5.0.0. Making > iOS version of app. MacBook Pro (pre-Retina version). >Reporter: Steve Husting > Fix For: Master > > > After adding inAppBrowser to config.xml as > > > > then running cordova prepare ios, get error in CLI: > Parsing /Users/dragonhu/Documents/PhoneGap_apps/gothic2015/config.xml failed > Error: Unexpected close tag > Line: 28 > Column: 9 > Char: > > ... that is the end > of -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8911) cordova prepare ios complains of "Error: Unexpected close tag" for ""
[ https://issues.apache.org/jira/browse/CB-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512731#comment-14512731 ] Steve Husting commented on CB-8911: --- The above error also occurs if I do cordova platform save and cordova plugin save after the above issue. > cordova prepare ios complains of "Error: Unexpected close tag" for > "" > --- > > Key: CB-8911 > URL: https://issues.apache.org/jira/browse/CB-8911 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, iOS >Affects Versions: 3.5.0 > Environment: Mac OS X Yosemite 10.10.3. cordova -v = 5.0.0. Making > iOS version of app. MacBook Pro (pre-Retina version). >Reporter: Steve Husting > Fix For: Master > > > After adding inAppBrowser to config.xml as > > > > then running cordova prepare ios, get error in CLI: > Parsing /Users/dragonhu/Documents/PhoneGap_apps/gothic2015/config.xml failed > Error: Unexpected close tag > Line: 28 > Column: 9 > Char: > > ... that is the end > of -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-8911) cordova prepare ios complains of "Error: Unexpected close tag" for ""
Steve Husting created CB-8911: - Summary: cordova prepare ios complains of "Error: Unexpected close tag" for "" Key: CB-8911 URL: https://issues.apache.org/jira/browse/CB-8911 Project: Apache Cordova Issue Type: Bug Components: CLI, iOS Affects Versions: 3.5.0 Environment: Mac OS X Yosemite 10.10.3. cordova -v = 5.0.0. Making iOS version of app. MacBook Pro (pre-Retina version). Reporter: Steve Husting Fix For: Master After adding inAppBrowser to config.xml as then running cordova prepare ios, get error in CLI: Parsing /Users/dragonhu/Documents/PhoneGap_apps/gothic2015/config.xml failed Error: Unexpected close tag Line: 28 Column: 9 Char: > ... that is the end > of -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177408#comment-14177408 ] Steve Husting commented on CB-7809: --- If you never intended for cordova build android to copy screen image from one location to the /platforms/* location, then you should change the docs to reflect this: android/screen-hdpi-landscrape.png ... and so on should be changed to ... /platforms/android/res/drawable-land-hdpi/screen.png ... to be more accurate. Otherwise it seems that we are being asked to make a /myApp/android directory and include all those screen-*.png files in it, and they would be transferred over on cordova build. We get this impression because the icon files work that way. Why would the splashscreens be done differently from the icons? If we make all our Android screen names like screen-hdpi-landscrape.png as it says at the beginning of the online docs on splashscreens, then we need to change all the names to screen.png when we read further down the doc. That's part of the confusion: we create all our splashscreens in one /android folder with a long name, then we copy and rename all those files into the /platform/android/res/* folders. So in the final analysis, it appears that the docs mean for us to put the icons in /myApp/res* and reflect this folder structure in config.xml, then they'll be transferred over via config.xml. But there's no way to transfer over screen.png files built into cordova build android; we are to copy them directly into /platforms/android/res/*. But the earlier part of the docs seems to refute that because it states specific folders and filenames that contradict the idea of saving them directly into the /platforms folders. > Put default app images in www/res > - > > Key: CB-7809 > URL: https://issues.apache.org/jira/browse/CB-7809 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Affects Versions: 3.5.0 > Environment: Any Environment >Reporter: Steve Husting >Priority: Trivial > Labels: icons, splashscreen > > People are confused about how to update the splash screens during their > Android build. Why not place all the default app helloCordova icons and > splashes in the location you recommend, in /helloCordova/android/res/* > instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml > with the lines needed to port the files over to Android via CLI as you > recommend. > This example of proper placement and config.xml usage will remove all users' > doubts about where to put the icons and splashes. > I assume you could programmatically set up the default app so that the entire > /platforms/android/res folder structure is reproduced in > /helloCordova/android/res/ to make it easy to understand where to put the > user's own files. They'll replace those icon.pngs and screen.pngs with their > own. You would program the same thing with iOS files in > /hellocordova/ios/res/ . > Just a suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177203#comment-14177203 ] Steve Husting edited comment on CB-7809 at 10/20/14 6:38 PM: - Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). That way, all icons would be named "icon.png" and screens "screen.png" in order to fulfill Compounding the confusion is the fact that the preference name for the screen.png is "screen," yet in the documentation we are told that the screen images names should be "screen-hdpi-landscape.png" and so on. Nowhere in the documentation do we allow for all these names in the config.xml file -- just value="screen." value="screen" only makes sense if the myApp/platforms/android/* structure were set up as in /platforms/android/* where all the screen names will be consistently only "screen.png." was (Author: websteve): Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). That way, all icons would be named "icon.png" and screens "screen.png" in order to fulfill > Put default app images in www/res > - > > Key: CB-7809 > URL: https://issues.apache.org/jira/browse/CB-7809 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Affects Versions: 3.5.0 > Environment: Any Environment >Reporter: Steve Husting >Priority: Trivial > Labels: icons, splashscreen > > People are confused about how to update the splash screens during their > Android build. Why not place all the default app helloCordova icons and > splashes in the location you recommend, in /helloCordova/android/res/* > instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml > with the lines needed to port the files over to Android via CLI as you > recommend. > This example of proper placement and config.xml usage will remove all users' > doubts about where to put the icons and splashes. > I assume you could programmatically set up the default app so that the entire > /platforms/android/res folder structure is reproduced in > /helloCordova/android/res/ to make it easy to understand where to put the > user's own files. They'll replace those icon.pngs and screen.pngs with their > own. You would program the same thing with iOS files in > /hellocordova/ios/res/ . > Just a suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177203#comment-14177203 ] Steve Husting edited comment on CB-7809 at 10/20/14 6:23 PM: - Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). That way, all icons would be named "icon.png" and screens "screen.png" in order to fulfill was (Author: websteve): Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). > Put default app images in www/res > - > > Key: CB-7809 > URL: https://issues.apache.org/jira/browse/CB-7809 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Affects Versions: 3.5.0 > Environment: Any Environment >Reporter: Steve Husting >Priority: Trivial > Labels: icons, splashscreen > > People are confused about how to update the splash screens during their > Android build. Why not place all the default app helloCordova icons and > splashes in the location you recommend, in /helloCordova/android/res/* > instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml > with the lines needed to port the files over to Android via CLI as you > recommend. > This example of proper placement and config.xml usage will remove all users' > doubts about where to put the icons and splashes. > I assume you could programmatically set up the default app so that the entire > /platforms/android/res folder structure is reproduced in > /helloCordova/android/res/ to make it easy to understand where to put the > user's own files. They'll replace those icon.pngs and screen.pngs with their > own. You would program the same thing with iOS files in > /hellocordova/ios/res/ . > Just a suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177203#comment-14177203 ] Steve Husting edited comment on CB-7809 at 10/20/14 6:20 PM: - Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). was (Author: websteve): Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. > Put default app images in www/res > - > > Key: CB-7809 > URL: https://issues.apache.org/jira/browse/CB-7809 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Affects Versions: 3.5.0 > Environment: Any Environment >Reporter: Steve Husting >Priority: Trivial > Labels: icons, splashscreen > > People are confused about how to update the splash screens during their > Android build. Why not place all the default app helloCordova icons and > splashes in the location you recommend, in /helloCordova/android/res/* > instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml > with the lines needed to port the files over to Android via CLI as you > recommend. > This example of proper placement and config.xml usage will remove all users' > doubts about where to put the icons and splashes. > I assume you could programmatically set up the default app so that the entire > /platforms/android/res folder structure is reproduced in > /helloCordova/android/res/ to make it easy to understand where to put the > user's own files. They'll replace those icon.pngs and screen.pngs with their > own. You would program the same thing with iOS files in > /hellocordova/ios/res/ . > Just a suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177203#comment-14177203 ] Steve Husting edited comment on CB-7809 at 10/20/14 6:03 PM: - Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. was (Author: websteve): Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/ folder. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android location and wonder how to use the config.xml for icons and screens. If the myApp/res/ etc. folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. > Put default app images in www/res > - > > Key: CB-7809 > URL: https://issues.apache.org/jira/browse/CB-7809 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Affects Versions: 3.5.0 > Environment: Any Environment >Reporter: Steve Husting >Priority: Trivial > Labels: icons, splashscreen > > People are confused about how to update the splash screens during their > Android build. Why not place all the default app helloCordova icons and > splashes in the location you recommend, in /helloCordova/android/res/* > instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml > with the lines needed to port the files over to Android via CLI as you > recommend. > This example of proper placement and config.xml usage will remove all users' > doubts about where to put the icons and splashes. > I assume you could programmatically set up the default app so that the entire > /platforms/android/res folder structure is reproduced in > /helloCordova/android/res/ to make it easy to understand where to put the > user's own files. They'll replace those icon.pngs and screen.pngs with their > own. You would program the same thing with iOS files in > /hellocordova/ios/res/ . > Just a suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177203#comment-14177203 ] Steve Husting commented on CB-7809: --- Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/ folder. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android location and wonder how to use the config.xml for icons and screens. If the myApp/res/ etc. folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. > Put default app images in www/res > - > > Key: CB-7809 > URL: https://issues.apache.org/jira/browse/CB-7809 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Affects Versions: 3.5.0 > Environment: Any Environment >Reporter: Steve Husting >Priority: Trivial > Labels: icons, splashscreen > > People are confused about how to update the splash screens during their > Android build. Why not place all the default app helloCordova icons and > splashes in the location you recommend, in /helloCordova/android/res/* > instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml > with the lines needed to port the files over to Android via CLI as you > recommend. > This example of proper placement and config.xml usage will remove all users' > doubts about where to put the icons and splashes. > I assume you could programmatically set up the default app so that the entire > /platforms/android/res folder structure is reproduced in > /helloCordova/android/res/ to make it easy to understand where to put the > user's own files. They'll replace those icon.pngs and screen.pngs with their > own. You would program the same thing with iOS files in > /hellocordova/ios/res/ . > Just a suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174038#comment-14174038 ] Steve Husting commented on CB-7665: --- This resolves the issue. I have fully documented the steps on my blog under VI.b Create a Signed Apk (CLI) at http://iphonedevlog.wordpress.com/2014/10/10/using-android-studio-beta-with-cordova-phonegap/ > Release process for Google Play has no documentation, requires guesswork! > -- > > Key: CB-7665 > URL: https://issues.apache.org/jira/browse/CB-7665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI, Docs >Affects Versions: 3.5.0 > Environment: Mac OS X Lion >Reporter: Steve Husting > Labels: patch > Fix For: 3.5.0 > > > I output my myApp version 12 project with: cordova build android --release > It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk > I changed the name to the final apk name: myApp-release-unsigned.apk = > myApp.apk > I copied the myApp.keystore file used on earlier myApps to the same folder. > Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA > -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp > I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk > When I uploaded the myApp.apk to Google Play, it said that the file needed to > be zipaligned. > The verbose output shows zipalign being done. So is there a bug when the apk > is made via cordova build android --release? > Is there a step missing that I should be taking? Unfortunately, all the > instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-7809) Put default app images in www/res
Steve Husting created CB-7809: - Summary: Put default app images in www/res Key: CB-7809 URL: https://issues.apache.org/jira/browse/CB-7809 Project: Apache Cordova Issue Type: Improvement Components: CordovaLib Affects Versions: 3.5.0 Environment: Any Environment Reporter: Steve Husting Priority: Trivial People are confused about how to update the splash screens during their Android build. Why not place all the default app helloCordova icons and splashes in the location you recommend, in /helloCordova/android/res/* instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml with the lines needed to port the files over to Android via CLI as you recommend. This example of proper placement and config.xml usage will remove all users' doubts about where to put the icons and splashes. I assume you could programmatically set up the default app so that the entire /platforms/android/res folder structure is reproduced in /helloCordova/android/res/ to make it easy to understand where to put the user's own files. They'll replace those icon.pngs and screen.pngs with their own. You would program the same thing with iOS files in /hellocordova/ios/res/ . Just a suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-7795) Android Studio Beta generates these errors
Steve Husting created CB-7795: - Summary: Android Studio Beta generates these errors Key: CB-7795 URL: https://issues.apache.org/jira/browse/CB-7795 Project: Apache Cordova Issue Type: Task Components: Android, CordovaLib Affects Versions: 3.5.0 Environment: Mac OS X, Android Studio Beta 0.8.9, Cordova 3.6.3 Reporter: Steve Husting Priority: Trivial When doing Analyze > Inspect Code (similar to a lint) in Android Studio Beta 0.8.9 on a Cordova 3.6.3 project, I get the following errors. This project was built as API 17. I prioritized it as Trivial because this is beta software. cordovaWebView.java Error:266, 35 java: cannot find symbol, KITKAT Error:230, 79 java: cannot find symbol, KITKAT Error:269, 20 java: cannot find symbol, KITKAT IceCreamCordovaWebViewclient.java Error:85, 82 java: cannot find symbol, KITKAT HttpsURLConnectionImpl.java Error:347, 3 java: method does not override or implement a method from a supertype I followed the steps here to make the app: http://iphonedevlog.wordpress.com/2014/10/10/using-android-studio-beta-with-cordova-phonegap/ -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-7752) cordova platform add android won't create platform because it wants android-19 installed
Steve Husting created CB-7752: - Summary: cordova platform add android won't create platform because it wants android-19 installed Key: CB-7752 URL: https://issues.apache.org/jira/browse/CB-7752 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.5.0 Environment: Mac 10.5.6 Cordova CLI 3.6.3 Reporter: Steve Husting Fix For: 3.6.3 I followed these steps: npm update -g cordova cordova -v [returned 3.6.3...] cordova create helloCordova cd helloCordova cordova platform add android After the line, "Creating android project..." is the error message: 'Please install Android target "android-19". Hint: Run "android" from your command-line to open the SDK Manager.' I went ahead and ran android to install android-19. Is this really supposed to happen for a new project? I though we were supposed to determine on our own what versions we want to support. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158163#comment-14158163 ] Steve Husting edited comment on CB-7665 at 10/3/14 4:36 PM: 1. I created a text file called ant.properties and saved it in the root myApp/ folder. I copied my .keystore to the same folder. The contents of the file: # key.store = path/to/.keystore file # key.alias = alias key.store=myApp.keystore key.alias=myApp 2. I ran in the terminal: $ cd myApp/platforms/android $ ant release ... and got the message: BUILD FAILED /Users/Steve/Documents/AndroidApps/myApp/platforms/android/build.xml:55: sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable. 3. Running ... android update project ... gets ... Error: The parameter --path must be defined for action 'update project' 4. I don't understand how to formulate the recommended command: android update project --path What folder should the path point to? was (Author: websteve): 1. I created a text file called ant.properties and saved it in the root myApp/ folder. I copied my .keystore to the same folder. The contents of the file: # key.store = path/to/.keystore file # key.alias = alias key.store=myApp.keystore key.alias=myApp 2. I ran in the terminal: $ cd myApp/platforms/android $ ant release ... and got the message: BUILD FAILED /Users/Steve/Documents/AndroidApps/myApp/platforms/android/build.xml:55: sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable. 3. I don't understand how to formulate the recommended command: android update project --path > Release process for Google Play has no documentation, requires guesswork! > -- > > Key: CB-7665 > URL: https://issues.apache.org/jira/browse/CB-7665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI, Docs >Affects Versions: 3.5.0 > Environment: Mac OS X Lion >Reporter: Steve Husting > Labels: patch > Fix For: 3.5.0 > > > I output my myApp version 12 project with: cordova build android --release > It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk > I changed the name to the final apk name: myApp-release-unsigned.apk = > myApp.apk > I copied the myApp.keystore file used on earlier myApps to the same folder. > Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA > -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp > I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk > When I uploaded the myApp.apk to Google Play, it said that the file needed to > be zipaligned. > The verbose output shows zipalign being done. So is there a bug when the apk > is made via cordova build android --release? > Is there a step missing that I should be taking? Unfortunately, all the > instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158163#comment-14158163 ] Steve Husting commented on CB-7665: --- 1. I created a text file called ant.properties and saved it in the root myApp/ folder. I copied my .keystore to the same folder. The contents of the file: # key.store = path/to/.keystore file # key.alias = alias key.store=myApp.keystore key.alias=myApp 2. I ran in the terminal: $ cd myApp/platforms/android $ ant release ... and got the message: BUILD FAILED /Users/Steve/Documents/AndroidApps/myApp/platforms/android/build.xml:55: sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable. 3. I don't understand how to formulate the recommended command: android update project --path > Release process for Google Play has no documentation, requires guesswork! > -- > > Key: CB-7665 > URL: https://issues.apache.org/jira/browse/CB-7665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI, Docs >Affects Versions: 3.5.0 > Environment: Mac OS X Lion >Reporter: Steve Husting > Labels: patch > Fix For: 3.5.0 > > > I output my myApp version 12 project with: cordova build android --release > It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk > I changed the name to the final apk name: myApp-release-unsigned.apk = > myApp.apk > I copied the myApp.keystore file used on earlier myApps to the same folder. > Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA > -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp > I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk > When I uploaded the myApp.apk to Google Play, it said that the file needed to > be zipaligned. > The verbose output shows zipalign being done. So is there a bug when the apk > is made via cordova build android --release? > Is there a step missing that I should be taking? Unfortunately, all the > instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153368#comment-14153368 ] Steve Husting commented on CB-7665: --- Hi Michael, When I opened project.properties, it says, "Do not modify this file -- YOUR CHANGES WILL BE ERASED!" I suspect you mean the ant.projects file, which must be in another directory. > Release process for Google Play has no documentation, requires guesswork! > -- > > Key: CB-7665 > URL: https://issues.apache.org/jira/browse/CB-7665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI, Docs >Affects Versions: 3.5.0 > Environment: Mac OS X Lion >Reporter: Steve Husting > Labels: patch > Fix For: 3.5.0 > > > I output my myApp version 12 project with: cordova build android --release > It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk > I changed the name to the final apk name: myApp-release-unsigned.apk = > myApp.apk > I copied the myApp.keystore file used on earlier myApps to the same folder. > Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA > -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp > I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk > When I uploaded the myApp.apk to Google Play, it said that the file needed to > be zipaligned. > The verbose output shows zipalign being done. So is there a bug when the apk > is made via cordova build android --release? > Is there a step missing that I should be taking? Unfortunately, all the > instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153348#comment-14153348 ] Steve Husting commented on CB-7665: --- Hi Joe, "It just works" is confusing me. Are the steps I took in the Description the correct steps, or is something missing? Because it does not work for me, sorry! I'm not receiving any alternate concrete steps to take. :) > Release process for Google Play has no documentation, requires guesswork! > -- > > Key: CB-7665 > URL: https://issues.apache.org/jira/browse/CB-7665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI, Docs >Affects Versions: 3.5.0 > Environment: Mac OS X Lion >Reporter: Steve Husting > Labels: patch > Fix For: 3.5.0 > > > I output my myApp version 12 project with: cordova build android --release > It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk > I changed the name to the final apk name: myApp-release-unsigned.apk = > myApp.apk > I copied the myApp.keystore file used on earlier myApps to the same folder. > Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA > -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp > I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk > When I uploaded the myApp.apk to Google Play, it said that the file needed to > be zipaligned. > The verbose output shows zipalign being done. So is there a bug when the apk > is made via cordova build android --release? > Is there a step missing that I should be taking? Unfortunately, all the > instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153335#comment-14153335 ] Steve Husting commented on CB-7665: --- Thank you, Michael. If you look in the description, you'll see the steps I've taken. Can you tell me what should change? As far as I know, they are correct. According to Joe Bowser on this page, "The CLI doesn't handle any of the release steps for Android. This needs to change." > Release process for Google Play has no documentation, requires guesswork! > -- > > Key: CB-7665 > URL: https://issues.apache.org/jira/browse/CB-7665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI, Docs >Affects Versions: 3.5.0 > Environment: Mac OS X Lion >Reporter: Steve Husting > Labels: patch > Fix For: 3.5.0 > > > I output my myApp version 12 project with: cordova build android --release > It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk > I changed the name to the final apk name: myApp-release-unsigned.apk = > myApp.apk > I copied the myApp.keystore file used on earlier myApps to the same folder. > Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA > -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp > I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk > When I uploaded the myApp.apk to Google Play, it said that the file needed to > be zipaligned. > The verbose output shows zipalign being done. So is there a bug when the apk > is made via cordova build android --release? > Is there a step missing that I should be taking? Unfortunately, all the > instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153319#comment-14153319 ] Steve Husting commented on CB-7665: --- Hi Michael, Are you saying that the Google directions you mentioned for "ant build" understands the Cordova folder structure and will build an apk from it? We don't use the keytool and jarsigner commands at all? Only zipalign after ant build? This is hard to believe, sorry. > Release process for Google Play has no documentation, requires guesswork! > -- > > Key: CB-7665 > URL: https://issues.apache.org/jira/browse/CB-7665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI, Docs >Affects Versions: 3.5.0 > Environment: Mac OS X Lion >Reporter: Steve Husting > Labels: patch > Fix For: 3.5.0 > > > I output my myApp version 12 project with: cordova build android --release > It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk > I changed the name to the final apk name: myApp-release-unsigned.apk = > myApp.apk > I copied the myApp.keystore file used on earlier myApps to the same folder. > Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA > -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp > I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk > When I uploaded the myApp.apk to Google Play, it said that the file needed to > be zipaligned. > The verbose output shows zipalign being done. So is there a bug when the apk > is made via cordova build android --release? > Is there a step missing that I should be taking? Unfortunately, all the > instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7665) Google Play does not detect zipalign in corova build android --release apk
[ https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152488#comment-14152488 ] Steve Husting commented on CB-7665: --- zipalign manually also results in error. Unable to figure out what steps in CLI to output Google Play-ready apk. > Google Play does not detect zipalign in corova build android --release apk > -- > > Key: CB-7665 > URL: https://issues.apache.org/jira/browse/CB-7665 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI >Affects Versions: 3.5.0 > Environment: Mac OS X Lion >Reporter: Steve Husting > Labels: patch > Fix For: 3.5.0 > > > I output my myApp version 12 project with: cordova build android --release > It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk > I changed the name to the final apk name: myApp-release-unsigned.apk = > myApp.apk > I copied the myApp.keystore file used on earlier myApps to the same folder. > Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA > -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp > I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk > When I uploaded the myApp.apk to Google Play, it said that the file needed to > be zipaligned. > The verbose output shows zipalign being done. So is there a bug when the apk > is made via cordova build android --release? > Is there a step missing that I should be taking? Unfortunately, all the > instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7665) Google Play does not detect zipalign in corova build android --release apk
Steve Husting created CB-7665: - Summary: Google Play does not detect zipalign in corova build android --release apk Key: CB-7665 URL: https://issues.apache.org/jira/browse/CB-7665 Project: Apache Cordova Issue Type: Bug Components: Android, CLI Affects Versions: 3.5.0 Environment: Mac OS X Lion Reporter: Steve Husting Priority: Critical Fix For: 3.5.0 I output my myApp version 12 project with: cordova build android --release It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk I changed the name to the final apk name: myApp-release-unsigned.apk = myApp.apk I copied the myApp.keystore file used on earlier myApps to the same folder. Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore myApp.keystore myApp.apk myApp I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk When I uploaded the myApp.apk to Google Play, it said that the file needed to be zipaligned. The verbose output shows zipalign being done. So is there a bug when the apk is made via cordova build android --release? Is there a step missing that I should be taking? Unfortunately, all the instructions for this on the Internet assume I'm not using Cordova. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7022) Xcode scheme mixed up with config.xml changes
[ https://issues.apache.org/jira/browse/CB-7022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043799#comment-14043799 ] Steve Husting commented on CB-7022: --- I reverted to 3.4.0 and got the same problem. I changed the name in config.xml and the scheme in Xcode no longer allowed me to build and run the app in the device. That is, the device name would not appear in the scheme unless I selected CordovaLib, and even then it would build but not run in the device. I changed the name back in config.xml and the scheme in Xcode worked again. > Xcode scheme mixed up with config.xml changes > - > > Key: CB-7022 > URL: https://issues.apache.org/jira/browse/CB-7022 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaJS >Affects Versions: 3.5.0 > Environment: Mac OS X 10.9.3 on latest Mac Mini > Cordova CLI 3.5.0 (cordova, not phonegap) > Testing on iPod touch with iOS 6.0.1 >Reporter: Steve Husting > Fix For: 3.6.0 > > > At first, the default project was called HelloCordova by Cordova in > config.xml entered "My App" in what changes in the build. > What happened in Xcode is that all those are being remembered in the Xcode > scheme -- all except the current myApp! The HelloCordova and My App both > default to Mac OS X in the scheme, and the only other selectable scheme is > CordovaLib. At this point I'm unable to test this app on my device. > Never had this issue before 3.5.0. With each permutation, I do a cordova > prepare ios, double-click on the myApp.xcodeproj file in /platforms/ios, then > option/Project > Clean Build Folder. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-7022) Xcode scheme mixed up with config.xml changes
Steve Husting created CB-7022: - Summary: Xcode scheme mixed up with config.xml changes Key: CB-7022 URL: https://issues.apache.org/jira/browse/CB-7022 Project: Apache Cordova Issue Type: Bug Components: CordovaJS Affects Versions: 3.5.0 Environment: Mac OS X 10.9.3 on latest Mac Mini Cordova CLI 3.5.0 (cordova, not phonegap) Testing on iPod touch with iOS 6.0.1 Reporter: Steve Husting Fix For: 3.6.0 At first, the default project was called HelloCordova by Cordova in config.xml Clean Build Folder. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CB-6891) Splashscreen CLI URL results in "No such file or directory"
[ https://issues.apache.org/jira/browse/CB-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Husting closed CB-6891. - Resolution: Fixed Fix Version/s: 3.0.0 Error in my thinking about the problem. > Splashscreen CLI URL results in "No such file or directory" > --- > > Key: CB-6891 > URL: https://issues.apache.org/jira/browse/CB-6891 > Project: Apache Cordova > Issue Type: Task > Components: CLI >Affects Versions: 3.4.0 > Environment: Mac OS X 10.9.1 on latest Mac Mini > Cordova CLI 3.4.0 > for Android 4.3, 4.4 v19 >Reporter: Steve Husting > Labels: documentation > Fix For: 3.0.0 > > > This page: > http://docs.phonegap.com/en/3.0.0/cordova_splashscreen_splashscreen.md.html#Splashscreen > ... tells us to use the following to get the Splashscreen API with CLI: > cordova plugin add > https://git-wip-us.apache.org/repos/asf/cordova-plugin-splashscreen.git > When I do that I get the console response: > -bash: > https://git-wip-us.apache.org/repos/asf/cordova-plugin-splashscreen.git: No > such file or directory > With cordova plugin list, it shows no splashscreen plugin listed. > Conclusion: we need the plugin's URL updated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6891) Splashscreen CLI URL results in "No such file or directory"
[ https://issues.apache.org/jira/browse/CB-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020394#comment-14020394 ] Steve Husting commented on CB-6891: --- I was wrong. That is the correct URL for 3.0.0. I needed to use the URL in 3.4.0. This can be closed. > Splashscreen CLI URL results in "No such file or directory" > --- > > Key: CB-6891 > URL: https://issues.apache.org/jira/browse/CB-6891 > Project: Apache Cordova > Issue Type: Task > Components: CLI >Affects Versions: 3.4.0 > Environment: Mac OS X 10.9.1 on latest Mac Mini > Cordova CLI 3.4.0 > for Android 4.3, 4.4 v19 >Reporter: Steve Husting > Labels: documentation > > This page: > http://docs.phonegap.com/en/3.0.0/cordova_splashscreen_splashscreen.md.html#Splashscreen > ... tells us to use the following to get the Splashscreen API with CLI: > cordova plugin add > https://git-wip-us.apache.org/repos/asf/cordova-plugin-splashscreen.git > When I do that I get the console response: > -bash: > https://git-wip-us.apache.org/repos/asf/cordova-plugin-splashscreen.git: No > such file or directory > With cordova plugin list, it shows no splashscreen plugin listed. > Conclusion: we need the plugin's URL updated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6891) Splashscreen CLI URL results in "No such file or directory"
Steve Husting created CB-6891: - Summary: Splashscreen CLI URL results in "No such file or directory" Key: CB-6891 URL: https://issues.apache.org/jira/browse/CB-6891 Project: Apache Cordova Issue Type: Task Components: CLI Affects Versions: 3.4.0 Environment: Mac OS X 10.9.1 on latest Mac Mini Cordova CLI 3.4.0 for Android 4.3, 4.4 v19 Reporter: Steve Husting This page: http://docs.phonegap.com/en/3.0.0/cordova_splashscreen_splashscreen.md.html#Splashscreen ... tells us to use the following to get the Splashscreen API with CLI: cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-splashscreen.git When I do that I get the console response: -bash: https://git-wip-us.apache.org/repos/asf/cordova-plugin-splashscreen.git: No such file or directory With cordova plugin list, it shows no splashscreen plugin listed. Conclusion: we need the plugin's URL updated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-4729) "cordova emulate android" does not run emulator
[ https://issues.apache.org/jira/browse/CB-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778877#comment-13778877 ] Steve Husting commented on CB-4729: --- Thank you! > "cordova emulate android" does not run emulator > --- > > Key: CB-4729 > URL: https://issues.apache.org/jira/browse/CB-4729 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OS X >Reporter: Steve Husting >Assignee: Braden Shepherdson > > When I run "cordova emulate android" then the screen flickers about 20 > seconds later, but no emulator appears. The Eclipse SDK is installed and I've > created other apps with it pre-CLI 3.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4729) "cordova emulate android" does not run emulator
[ https://issues.apache.org/jira/browse/CB-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778845#comment-13778845 ] Steve Husting commented on CB-4729: --- "cordova emulate android --verbose" Returns: Steve$ cordova emulate android --verbose cordova library for "android" already exists. No need to download. Continuing. Wrote out Android application name to "RC10 Classic Essentials" Wrote out Android package name to "com.teamassociated.RC10ClassicEssentials" Calling plugman.prepare for platform "android" Preparing android project... Processing configuration changes for plugins. Iterating over installed plugins: [] Writing out cordova_plugins.js... Running on emulator for platform "android" via command ""/Users/Steve/Documents/AndroidApps/RC10ClassicEssentials/platforms/android/cordova/run" --emulator" (output to follow)... [20 minutes later, nothing has happened.] > "cordova emulate android" does not run emulator > --- > > Key: CB-4729 > URL: https://issues.apache.org/jira/browse/CB-4729 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OS X >Reporter: Steve Husting >Assignee: Braden Shepherdson > > When I run "cordova emulate android" then the screen flickers about 20 > seconds later, but no emulator appears. The Eclipse SDK is installed and I've > created other apps with it pre-CLI 3.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4729) "cordova emulate android" does not run emulator
[ https://issues.apache.org/jira/browse/CB-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778083#comment-13778083 ] Steve Husting commented on CB-4729: --- Trying from the root folder: cordova/run --emulate Returns: [command prompt] Trying from the root folder: cordova run --emulate Returns: [command prompt] Nothing happens; nothing else starts; just a near-quick return to the command prompt. -- Regards, Steve Husting, Webmaster Team Associated > "cordova emulate android" does not run emulator > --- > > Key: CB-4729 > URL: https://issues.apache.org/jira/browse/CB-4729 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OS X >Reporter: Steve Husting >Assignee: Braden Shepherdson > > When I run "cordova emulate android" then the screen flickers about 20 > seconds later, but no emulator appears. The Eclipse SDK is installed and I've > created other apps with it pre-CLI 3.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4713) "jarsigner: unable to sign jar" error message
[ https://issues.apache.org/jira/browse/CB-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778051#comment-13778051 ] Steve Husting commented on CB-4713: --- Everything is fine if I use Eclipse. I didn't know where CLI stopped and Eclipse began. Thanks! -- Regards, Steve Husting, Webmaster Team Associated > "jarsigner: unable to sign jar" error message > - > > Key: CB-4713 > URL: https://issues.apache.org/jira/browse/CB-4713 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX >Reporter: Steve Husting >Assignee: Braden Shepherdson >Priority: Minor > Fix For: 3.0.0 > > > When I'm ready to do a final v1 apk, I run: > keytool -genkey -v -alias TestApp2 -keyalg RSA -keysize 2048 -validity 1 > -keystore TestApp2.keystore > I copy the TestApp2.keystore file to the TestApp2/platforms/android/bin > folder, where my TestApp2-debug.apk was created. > When I used jarsigner like so: > jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore > TestApp2.keystore -keypass 6charpassword TestApp2-debug.apk TestApp2 > ... sometimes I get the return from terminal: > jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry > compressed size (expected 15088 but got 15506 bytes) > This error comes because it has already been signed. Does this mean that > "cordova build android" is automatically applying the .keystore file in the > TestApp2/ folder, and we no longer need to do a jarsigner after the > first-time keytool has been applied? I thought we would be using jarsigner > for each build, each version. > Does cordova build android recognize the version number and applies the same > keytool to the same version? Not sure what's happening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4713) "jarsigner: unable to sign jar" error message
[ https://issues.apache.org/jira/browse/CB-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758232#comment-13758232 ] Steve Husting commented on CB-4713: --- I have not attempted this in Eclipse (there is no Eclipse project for it). I picked up the jarsign code from the Android Developer pages, Publishing > Signing your app. > "jarsigner: unable to sign jar" error message > - > > Key: CB-4713 > URL: https://issues.apache.org/jira/browse/CB-4713 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX >Reporter: Steve Husting >Assignee: Braden Shepherdson >Priority: Minor > Fix For: 3.0.0 > > > When I'm ready to do a final v1 apk, I run: > keytool -genkey -v -alias TestApp2 -keyalg RSA -keysize 2048 -validity 1 > -keystore TestApp2.keystore > I copy the TestApp2.keystore file to the TestApp2/platforms/android/bin > folder, where my TestApp2-debug.apk was created. > When I used jarsigner like so: > jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore > TestApp2.keystore -keypass 6charpassword TestApp2-debug.apk TestApp2 > ... sometimes I get the return from terminal: > jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry > compressed size (expected 15088 but got 15506 bytes) > This error comes because it has already been signed. Does this mean that > "cordova build android" is automatically applying the .keystore file in the > TestApp2/ folder, and we no longer need to do a jarsigner after the > first-time keytool has been applied? I thought we would be using jarsigner > for each build, each version. > Does cordova build android recognize the version number and applies the same > keytool to the same version? Not sure what's happening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4713) "jarsigner: unable to sign jar" error message
[ https://issues.apache.org/jira/browse/CB-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758214#comment-13758214 ] Steve Husting commented on CB-4713: --- It definitely gives the error consistently after I created the .keytool file. > "jarsigner: unable to sign jar" error message > - > > Key: CB-4713 > URL: https://issues.apache.org/jira/browse/CB-4713 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX >Reporter: Steve Husting >Assignee: Braden Shepherdson >Priority: Minor > Fix For: 3.0.0 > > > When I'm ready to do a final v1 apk, I run: > keytool -genkey -v -alias TestApp2 -keyalg RSA -keysize 2048 -validity 1 > -keystore TestApp2.keystore > I copy the TestApp2.keystore file to the TestApp2/platforms/android/bin > folder, where my TestApp2-debug.apk was created. > When I used jarsigner like so: > jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore > TestApp2.keystore -keypass 6charpassword TestApp2-debug.apk TestApp2 > ... sometimes I get the return from terminal: > jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry > compressed size (expected 15088 but got 15506 bytes) > This error comes because it has already been signed. Does this mean that > "cordova build android" is automatically applying the .keystore file in the > TestApp2/ folder, and we no longer need to do a jarsigner after the > first-time keytool has been applied? I thought we would be using jarsigner > for each build, each version. > Does cordova build android recognize the version number and applies the same > keytool to the same version? Not sure what's happening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4713) "jarsigner: unable to sign jar" error message
[ https://issues.apache.org/jira/browse/CB-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758010#comment-13758010 ] Steve Husting commented on CB-4713: --- I always drag the apk file to Dropbox, and it disappears from the bin folder. So it is rebuilt every time I use cordova build android. If you are confused, then I guess I'm using the right jarsigner commands after all (I've been accustomed to signing in Eclipse). Thanks! Steve H > "jarsigner: unable to sign jar" error message > - > > Key: CB-4713 > URL: https://issues.apache.org/jira/browse/CB-4713 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OSX >Reporter: Steve Husting >Assignee: Braden Shepherdson >Priority: Minor > Fix For: 3.0.0 > > > When I'm ready to do a final v1 apk, I run: > keytool -genkey -v -alias TestApp2 -keyalg RSA -keysize 2048 -validity 1 > -keystore TestApp2.keystore > I copy the TestApp2.keystore file to the TestApp2/platforms/android/bin > folder, where my TestApp2-debug.apk was created. > When I used jarsigner like so: > jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore > TestApp2.keystore -keypass 6charpassword TestApp2-debug.apk TestApp2 > ... sometimes I get the return from terminal: > jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry > compressed size (expected 15088 but got 15506 bytes) > This error comes because it has already been signed. Does this mean that > "cordova build android" is automatically applying the .keystore file in the > TestApp2/ folder, and we no longer need to do a jarsigner after the > first-time keytool has been applied? I thought we would be using jarsigner > for each build, each version. > Does cordova build android recognize the version number and applies the same > keytool to the same version? Not sure what's happening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4729) "cordova emulate android" does not run emulator
[ https://issues.apache.org/jira/browse/CB-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758001#comment-13758001 ] Steve Husting commented on CB-4729: --- "Try cordova/run --emulator instead." Returns: -bash: cordova/run: No such file or directory Regards, Steve Husting > "cordova emulate android" does not run emulator > --- > > Key: CB-4729 > URL: https://issues.apache.org/jira/browse/CB-4729 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OS X >Reporter: Steve Husting >Assignee: Braden Shepherdson > > When I run "cordova emulate android" then the screen flickers about 20 > seconds later, but no emulator appears. The Eclipse SDK is installed and I've > created other apps with it pre-CLI 3.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4729) "cordova emulate android" does not run emulator
[ https://issues.apache.org/jira/browse/CB-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757882#comment-13757882 ] Steve Husting commented on CB-4729: --- Try the following: cd platforms/android cordova/run --emulate It returns: Error: '--emulate' is not recognized as an install option Thanks! Steve Husting > "cordova emulate android" does not run emulator > --- > > Key: CB-4729 > URL: https://issues.apache.org/jira/browse/CB-4729 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OS X >Reporter: Steve Husting >Assignee: Braden Shepherdson > > When I run "cordova emulate android" then the screen flickers about 20 > seconds later, but no emulator appears. The Eclipse SDK is installed and I've > created other apps with it pre-CLI 3.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4729) "cordova emulate android" does not run emulator
Steve Husting created CB-4729: - Summary: "cordova emulate android" does not run emulator Key: CB-4729 URL: https://issues.apache.org/jira/browse/CB-4729 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Environment: Mac OS X Reporter: Steve Husting Assignee: Braden Shepherdson When I run "cordova emulate android" then the screen flickers about 20 seconds later, but no emulator appears. The Eclipse SDK is installed and I've created other apps with it pre-CLI 3.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4728) jarsigner does not always work
Steve Husting created CB-4728: - Summary: jarsigner does not always work Key: CB-4728 URL: https://issues.apache.org/jira/browse/CB-4728 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Environment: Mac OS X Reporter: Steve Husting Assignee: Braden Shepherdson Fix For: 3.0.0 When I used jarsigner like so: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore TestApp2.keystore -keypass 6charpassword TestApp2-debug.apk TestApp2 ... sometimes I get the return from terminal: jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size (expected 15088 but got 15506 bytes) This error comes because it has already been signed. Does this mean that "cordova build android" is automatically applying the .keystore file in the TestApp2/ folder, and we no longer need to do a jarsigner after the first keytool has been applied? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4713) "jarsigner: unable to sign jar" error message
Steve Husting created CB-4713: - Summary: "jarsigner: unable to sign jar" error message Key: CB-4713 URL: https://issues.apache.org/jira/browse/CB-4713 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Environment: Mac OSX Reporter: Steve Husting Assignee: Filip Maj Priority: Minor Fix For: 3.0.0 When I'm ready to do a final v1 apk, I run: keytool -genkey -v -alias TestApp2 -keyalg RSA -keysize 2048 -validity 1 -keystore TestApp2.keystore I copy the TestApp2.keystore file to the TestApp2/platforms/android/bin folder, where my TestApp2-debug.apk was created. When I used jarsigner like so: jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore TestApp2.keystore -keypass 6charpassword TestApp2-debug.apk TestApp2 ... sometimes I get the return from terminal: jarsigner: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size (expected 15088 but got 15506 bytes) This error comes because it has already been signed. Does this mean that "cordova build android" is automatically applying the .keystore file in the TestApp2/ folder, and we no longer need to do a jarsigner after the first-time keytool has been applied? I thought we would be using jarsigner for each build, each version. Does cordova build android recognize the version number and applies the same keytool to the same version? Not sure what's happening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4694) CLI commands no longer work when going from 3.0.6 to 3.0.7
[ https://issues.apache.org/jira/browse/CB-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753928#comment-13753928 ] Steve Husting commented on CB-4694: --- Thank you! -- Regards, Steve Husting, Webmaster Team Associated > CLI commands no longer work when going from 3.0.6 to 3.0.7 > -- > > Key: CB-4694 > URL: https://issues.apache.org/jira/browse/CB-4694 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Max OSX >Reporter: Steve Husting >Assignee: Filip Maj > > *Every one* of my Cordova commands in Mac OSX terminal are now returning: > > env: node\r: No such file or directory > > ... after upgrading to 3.0.7. They worked fine before. I used the following > to upgrade: > sudo npm update -g cordova > I tried the command again and problem remains. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4694) CLI commands no longer work when going from 3.0.6 to 3.0.7
Steve Husting created CB-4694: - Summary: CLI commands no longer work when going from 3.0.6 to 3.0.7 Key: CB-4694 URL: https://issues.apache.org/jira/browse/CB-4694 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.0.0 Environment: Max OSX Reporter: Steve Husting Assignee: Filip Maj *Every one* of my Cordova commands in Mac OSX terminal are now returning: env: node\r: No such file or directory ... after upgrading to 3.0.7. They worked fine before. I used the following to upgrade: sudo npm update -g cordova I tried the command again and problem remains. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4646) Doing a build should compile only that platform's icons and splash screens
Steve Husting created CB-4646: - Summary: Doing a build should compile only that platform's icons and splash screens Key: CB-4646 URL: https://issues.apache.org/jira/browse/CB-4646 Project: Apache Cordova Issue Type: Improvement Components: CLI Affects Versions: 3.0.0 Environment: Terminal on the Mac Reporter: Steve Husting Assignee: Filip Maj Priority: Minor When I do a cordova build android, the default Hello World app provided by Cordova is 8.9MB. When I remove the folders in the www/ folder that are unrelated to the Android platform, then the size built is 2.9MB. Please set the code to understand that the platform name in the Build or Run commands (e.g., cordova build android) should copy over only that platform's icon and screen folders, and not the other ones. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4206) "An error occured during creation of ios sub-project"
[ https://issues.apache.org/jira/browse/CB-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708774#comment-13708774 ] Steve Husting commented on CB-4206: --- $ cordova platform add ios [Error: An error occured during creation of ios sub-project. /bin/sh: /Users/Steve/.cordova/lib/ios/cordova/2.9.0/bin/create: No such file or directory ] Webmaster2s-Mac-mini:TestApp Steve$ $ rm -rf ~/.cordova/lib/ios/cordova/2.9.0/ -bash: $: command not found Webmaster2s-Mac-mini:TestApp Steve$ rm -rf ~/.cordova/lib/ios/cordova/2.9.0/ Webmaster2s-Mac-mini:TestApp Steve$ cordova create ~/Documents/AndroidApps/MyApp com.stevehusting.MyApp MyApp Webmaster2s-Mac-mini:TestApp Steve$ cordova -d platform add ios Requesting https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=snapshot;h=2.9.0;sf=tgz... Download complete. Extracting... Checking if platform "ios" passes minimum requirements... Checking iOS requirements... Running "xcodebuild -version" (output to follow) Xcode 4.6.3 Build version 4H1503 Running bin/create for platform "ios" with command: ""/Users/Steve/.cordova/lib/ios/cordova/2.9.0/bin/create" --arc "/Users/Steve/Documents/AndroidApps/TestApp/platforms/ios" "com.stevehusting.TestApp" "TestApp"" (output to follow) cordova library for "ios" already exists. No need to download. Continuing. Wrote out iOS Bundle Identifier to "com.stevehusting.TestApp" Wrote out iOS Bundle Version to "0.0.1" Wrote out iOS Product Name to "TestApp" Calling plugman.prepare for platform "ios" Preparing ios project, starting with processing of config changes... Iterating over installed plugins... Writing out cordova_plugins.json... Writing out cordova_plugins.js... Mac-mini:TestApp Steve$ > "An error occured during creation of ios sub-project" > - > > Key: CB-4206 > URL: https://issues.apache.org/jira/browse/CB-4206 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 2.9.0 > Environment: Mac OSX 10.8.4 >Reporter: Steve Husting >Assignee: Filip Maj > Labels: patch > Fix For: 3.0.0 > > > I am carefully documenting my steps for creating an app using PhoneGap CLI to > share with others. I ran into an unexpected error. Here are the steps to the > error. I had already successfully created the folder with: > cordova create AAA com.myproject MyProject > I've also used Homebrew to successfully install the ios-sim. Here are the > steps after that: > Project Creation, PhoneGap CLI-style > 20. I wanted to create an app called TestApp in the folder > ./Documents/AndroidApps/TestApp. So I would build up the command line like: > cordova create ./Documents/AndroidApps/TestApp com.stevehusting.TestApp > TestApp > 21. After the create command, indicate what platform you are building. Make > sure the Terminal indicates that the current folder is the TestApp folder, > and type: > cordova platform add ios > I received the error when I started the command from the TestApp folder: > [Error: An error occured during creation of ios sub-project. /bin/sh: > /Users/Steve/.cordova/lib/ios/cordova/2.9.0/bin/create: No such file or > directory] > I asked the program to list the platforms associated: > cordova platform list > … and got the response: > No platforms added. Use `cordova platform add `. > This seems like circular reasoning! I had already installed node.js, and > followed the steps carefully in > http://photokandy.tumblr.com/post/46289610781/getting-started-with-cordova-cli > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4206) "An error occured during creation of ios sub-project"
Steve Husting created CB-4206: - Summary: "An error occured during creation of ios sub-project" Key: CB-4206 URL: https://issues.apache.org/jira/browse/CB-4206 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 2.9.0 Environment: Mac OSX 10.8.4 Reporter: Steve Husting Assignee: Filip Maj Fix For: 3.0.0 I am carefully documenting my steps for creating an app using PhoneGap CLI to share with others. I ran into an unexpected error. Here are the steps to the error. I had already successfully created the folder with: cordova create AAA com.myproject MyProject I've also used Homebrew to successfully install the ios-sim. Here are the steps after that: Project Creation, PhoneGap CLI-style 20. I wanted to create an app called TestApp in the folder ./Documents/AndroidApps/TestApp. So I would build up the command line like: cordova create ./Documents/AndroidApps/TestApp com.stevehusting.TestApp TestApp 21. After the create command, indicate what platform you are building. Make sure the Terminal indicates that the current folder is the TestApp folder, and type: cordova platform add ios I received the error when I started the command from the TestApp folder: [Error: An error occured during creation of ios sub-project. /bin/sh: /Users/Steve/.cordova/lib/ios/cordova/2.9.0/bin/create: No such file or directory] I asked the program to list the platforms associated: cordova platform list … and got the response: No platforms added. Use `cordova platform add `. This seems like circular reasoning! I had already installed node.js, and followed the steps carefully in http://photokandy.tumblr.com/post/46289610781/getting-started-with-cordova-cli -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3995) PG will not open external links in web browser on desktop during testing
Steve Husting created CB-3995: - Summary: PG will not open external links in web browser on desktop during testing Key: CB-3995 URL: https://issues.apache.org/jira/browse/CB-3995 Project: Apache Cordova Issue Type: Bug Components: CordovaJS Affects Versions: 2.7.0 Environment: Windows XP with Firefox and Google Chrome. Reporter: Steve Husting Assignee: Filip Maj Priority: Minor Fix For: 2.7.0 If I open my PG 2.7.0 (Android) HTML page in FF or Google, and click on a link formatted like this: http://www.teamassociated.com/cars_and_trucks/RC10B4.2/RSRTR/manuals_setups/', '_blank');"> I get a 2-line dialog like this, with the second line in a form field: ["http://www.teamassociated.com/cars_and_trucks/RC10B4.2/RSRTR/manuals_setups/","_blank",null] gap:["InAppBrowser","open","InAppBrowser550906394"] OK button, Cancel button Clicking on either button stops the action and the link is not followed through. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
