Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-8255] MobileWeb: Android 2.3.X Device Browser won't load projects

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2012-06-08T10:59:35.000+0000
Affected Version/sRelease 2.0.0, Release 1.8.2
Fix Version/sRelease 2.0.0, Sprint 2012-07
ComponentsMobileWeb
Labelsqe-mw020912, regression
ReporterDustin Hyde
AssigneeChris Barber
Created2012-03-23T15:28:36.000+0000
Updated2012-06-08T11:17:10.000+0000

Description

2.0.0.X: The default app run on the android 2.3 browser will only load the splash screen. 1.8.2: there is a blank white screen. 1.8.1: default app appears to run correctly Steps to Reproduce: 1. Create default project in studio. 2. Package app, run on server. 3. Access via device (Android 2.3). Expected Result: App should load. Actual Result: Only splash screen loads.

Comments

  1. Dustin Hyde 2012-03-23

    Same behavior for all templates and samples: New Project, Tabbed, Master/Detail, SingleWindow, RSS Reader, Kitchen Sink, Todo List
  2. Dustin Hyde 2012-03-23

    This problem looks specific to this particular Nexus S 2.3.6 Device Browser, as other 2.3 devices were able to load the projects. Here is the log error: E/browser (10552): Console: Uncaught illegal access http://172.16.1.7/NewProject/:11398
  3. Bryan Hughes 2012-03-23

    After testing, it has been determined that this bug is only on one select device, and that it isn't worth the time to fix. Maybe we can revisit it someday.
  4. Neeraj Gupta 2012-03-23

    We are now able to reproduce this issue on multiple phones including Chris's phone. We need to fix this issue.
  5. Chris Barber 2012-03-26

    Pull request: https://github.com/appcelerator/titanium_mobile/pull/1847
  6. Wilson Luu 2012-06-08

    Reopening bug. Cannot launch default TiMobile project on: Device: Droid 1 (2.2.3) SDK build: 2.1.0.v20120608070223 Runtime: v8 Titanium Studio, build: 2.1.0.201206071457
  7. Wilson Luu 2012-06-08

    Re-closing this bug and creating a new bug. After talking to Dustin, the bug that I found could be different.

JSON Source