[jira] [Commented] (CB-1185) When Application is placed in background and resumed, the UI is frozen
[ https://issues.apache.org/jira/browse/CB-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545292#comment-13545292 ] Lindsey Simon commented on CB-1185: --- For some closure on this - I think what fixed it for us was some handing of pause/resume with on short timeouts and with canceling on one or the other to deal with pause and resume being called nearly back to back and perhaps twice really close together when we would come up. Especially happens when we'd resume from a notification intent. > When Application is placed in background and resumed, the UI is frozen > -- > > Key: CB-1185 > URL: https://issues.apache.org/jira/browse/CB-1185 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 2.0.0 > Environment: Jelly Bean 4.1, ICS 4.0.x >Reporter: Greg >Assignee: Joe Bowser > Attachments: 0001-Fix-issue-with-pause-resume-freezing-the-UI.patch, > 0002-Uncomment.patch, cordova-2.0.0.jar, issues.zip > > > When using PhoneGap 2.0.0 on ICS or JellyBean, the application freezes up > after you set the app to the background or turn of the screen. After around > 3-7 seconds, the application unfreezes and pretty much causes a panic and > usually crashes. No error reports have been submitted. > Here is how you re-produce the issue: > 1. Download Untappd - > V2.0.4(https://play.google.com/store/apps/details?id=com.untappdllc.app) > 2. After logging in stay on the Friends tab > 3. Turn the the screen off and wait about 3-7 minutes > 4. Turn the screen back on, and the interface should be frozen. > Another possible path to re-producing the issue: > 1. Download Untappd - > V2.0.4(https://play.google.com/store/apps/details?id=com.untappdllc.app) > 2. After logging in stay on the Friends tab > 3. Go back to the home screen then use other apps for about 3-7 minutes. > 4. Go back into Untappd, and the interface should be frozen. > When the app is frozen, native menu buttons will not nor any options in the > UI. > Would love to see if anyone can replicate this. I've tested this on Jelly > Bean 4.1.x on a Samsung Galaxy Nexus, but users have been having this problem > majority on ICS (4.0.x) > Thanks, > Greg -- 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
Re: Review of Core Platforms
Ok. So I removed 'sunrise', updated the definition text to include what was discussed here, and moved Bada to sunset. I noticed Windows 8 made its way into our core platforms without any mention in this thread. I have no objection to this, though I'm not sure it implements the entirety of the definition we describe. On Sat, Jan 5, 2013 at 4:50 AM, Anis KADRI wrote: > +1 for bada removal from core platforms. Samsung is not even working on it > anymore. "We're focused on Tizen" is what their marketing people told me > last time I asked them about it. > I think we should ship only platforms that matter (i.e platforms that > appear on Analyst's market share numbers) and document how to build the > others from source (because people do use them even if they're not > necessarily loud about it). > > > On Sat, Jan 5, 2013 at 3:32 AM, Filip Maj wrote: > >> >> >Think its still good to make this distinction even though our scope is >> >going to drastically reduce (in a sense). The benefit of these labels >> >is to indicate how much involvement developers using Cordova can >> >expect the Cordova platform to maintain. >> > >> >Core platforms target an operating system, with devices in >> >circulation, providing: >> > >> >- A standard low level bridge API and utilities. >> >- Standard set of low level CLI tools >> >- Embeddable (if possible) >> >- InAppBrowser and other browser-ish shims like alerts, etc. >> >- [what else?] >> >> A native plugin API? >> >>
Re: Review of Core Platforms
+1 for bada removal from core platforms. Samsung is not even working on it anymore. "We're focused on Tizen" is what their marketing people told me last time I asked them about it. I think we should ship only platforms that matter (i.e platforms that appear on Analyst's market share numbers) and document how to build the others from source (because people do use them even if they're not necessarily loud about it). On Sat, Jan 5, 2013 at 3:32 AM, Filip Maj wrote: > > >Think its still good to make this distinction even though our scope is > >going to drastically reduce (in a sense). The benefit of these labels > >is to indicate how much involvement developers using Cordova can > >expect the Cordova platform to maintain. > > > >Core platforms target an operating system, with devices in > >circulation, providing: > > > >- A standard low level bridge API and utilities. > >- Standard set of low level CLI tools > >- Embeddable (if possible) > >- InAppBrowser and other browser-ish shims like alerts, etc. > >- [what else?] > > A native plugin API? > >
Re: Review of Core Platforms
>Think its still good to make this distinction even though our scope is >going to drastically reduce (in a sense). The benefit of these labels >is to indicate how much involvement developers using Cordova can >expect the Cordova platform to maintain. > >Core platforms target an operating system, with devices in >circulation, providing: > >- A standard low level bridge API and utilities. >- Standard set of low level CLI tools >- Embeddable (if possible) >- InAppBrowser and other browser-ish shims like alerts, etc. >- [what else?] A native plugin API?
[jira] [Updated] (CB-2160) cordova_plist_to_config_xml fails inexplicably
[ https://issues.apache.org/jira/browse/CB-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen updated CB-2160: Description: Issue CB-1893 has apparently made it so you can update the plist to xml, however the documentation is non-existent, and amounts to the following 1 line in the upgrade guide. 10. Convert your Cordova.plist file to config.xml, by running the script bin/cordova_plist_to_config_xml on your project file. Here is what I get ... jessem-MacBookPro:ios jessem$ ./bin/cordova_plist_to_config_xml /Repos/RisingJ/BetaGap/Generic/HyperLab.xcodeproj Converting /Repos/RisingJ/BetaGap/Generic/Cordova.plist to /Repos/RisingJ/BetaGap/Generic/config.xml. Traceback (most recent call last): File "./bin/cordova_plist_to_config_xml", line 125, in main(sys.argv[1:]) File "./bin/cordova_plist_to_config_xml", line 115, in main ConvertPlist(plist_file, config_file) File "./bin/cordova_plist_to_config_xml", line 76, in ConvertPlist plist = plistlib.readPlist(src_path) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 78, in readPlist rootObject = p.parse(pathOrFile) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 406, in parse parser.ParseFile(fileobj) xml.parsers.expat.ExpatError: not well-formed (invalid token): line 1, column 9 was: Issue #1893 has apparently made it so you can update the plist to xml, however the documentation is non-existent, and amounts to the following 1 line in the upgrade guide. 10. Convert your Cordova.plist file to config.xml, by running the script bin/cordova_plist_to_config_xml on your project file. Here is what I get ... jessem-MacBookPro:ios jessem$ ./bin/cordova_plist_to_config_xml /Repos/RisingJ/BetaGap/Generic/HyperLab.xcodeproj Converting /Repos/RisingJ/BetaGap/Generic/Cordova.plist to /Repos/RisingJ/BetaGap/Generic/config.xml. Traceback (most recent call last): File "./bin/cordova_plist_to_config_xml", line 125, in main(sys.argv[1:]) File "./bin/cordova_plist_to_config_xml", line 115, in main ConvertPlist(plist_file, config_file) File "./bin/cordova_plist_to_config_xml", line 76, in ConvertPlist plist = plistlib.readPlist(src_path) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 78, in readPlist rootObject = p.parse(pathOrFile) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 406, in parse parser.ParseFile(fileobj) xml.parsers.expat.ExpatError: not well-formed (invalid token): line 1, column 9 > cordova_plist_to_config_xml fails inexplicably > -- > > Key: CB-2160 > URL: https://issues.apache.org/jira/browse/CB-2160 > Project: Apache Cordova > Issue Type: Bug > Components: Docs, iOS >Affects Versions: 2.3.0 > Environment: 2.3.0 >Reporter: Jesse MacFadyen >Assignee: Michael Brooks > > Issue CB-1893 has apparently made it so you can update the plist to xml, > however the documentation is non-existent, and amounts to the following 1 > line in the upgrade guide. > 10. Convert your Cordova.plist file to config.xml, by running the script > bin/cordova_plist_to_config_xml on your project file. > Here is what I get ... > jessem-MacBookPro:ios jessem$ ./bin/cordova_plist_to_config_xml > /Repos/RisingJ/BetaGap/Generic/HyperLab.xcodeproj > Converting /Repos/RisingJ/BetaGap/Generic/Cordova.plist to > /Repos/RisingJ/BetaGap/Generic/config.xml. > Traceback (most recent call last): > File "./bin/cordova_plist_to_config_xml", line 125, in > main(sys.argv[1:]) > File "./bin/cordova_plist_to_config_xml", line 115, in main > ConvertPlist(plist_file, config_file) > File "./bin/cordova_plist_to_config_xml", line 76, in ConvertPlist > plist = plistlib.readPlist(src_path) > File > "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", > line 78, in readPlist > rootObject = p.parse(pathOrFile) > File > "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", > line 406, in parse > parser.ParseFile(fileobj) > xml.parsers.expat.ExpatError: not well-formed (invalid token): line 1, column > 9 -- 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-2160) cordova_plist_to_config_xml fails inexplicably
Jesse MacFadyen created CB-2160: --- Summary: cordova_plist_to_config_xml fails inexplicably Key: CB-2160 URL: https://issues.apache.org/jira/browse/CB-2160 Project: Apache Cordova Issue Type: Bug Components: Docs, iOS Affects Versions: 2.3.0 Environment: 2.3.0 Reporter: Jesse MacFadyen Assignee: Michael Brooks Issue #1893 has apparently made it so you can update the plist to xml, however the documentation is non-existent, and amounts to the following 1 line in the upgrade guide. 10. Convert your Cordova.plist file to config.xml, by running the script bin/cordova_plist_to_config_xml on your project file. Here is what I get ... jessem-MacBookPro:ios jessem$ ./bin/cordova_plist_to_config_xml /Repos/RisingJ/BetaGap/Generic/HyperLab.xcodeproj Converting /Repos/RisingJ/BetaGap/Generic/Cordova.plist to /Repos/RisingJ/BetaGap/Generic/config.xml. Traceback (most recent call last): File "./bin/cordova_plist_to_config_xml", line 125, in main(sys.argv[1:]) File "./bin/cordova_plist_to_config_xml", line 115, in main ConvertPlist(plist_file, config_file) File "./bin/cordova_plist_to_config_xml", line 76, in ConvertPlist plist = plistlib.readPlist(src_path) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 78, in readPlist rootObject = p.parse(pathOrFile) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plistlib.py", line 406, in parse parser.ParseFile(fileobj) xml.parsers.expat.ExpatError: not well-formed (invalid token): line 1, column 9 -- 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
