Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-16618] Android: Unable to build app after update to SDK 3.2.2

GitHub Issuen/a
TypeBug
PriorityLow
StatusClosed
ResolutionInvalid
Resolution Date2014-03-24T20:25:06.000+0000
Affected Version/sRelease 3.2.2
Fix Version/sn/a
Componentsn/a
LabelssupportTeam
ReporterMarco Cota
AssigneeIngo Muschenetz
Created2014-03-12T19:09:19.000+0000
Updated2017-03-22T21:15:47.000+0000

Description

Issue

After upgrading to SDK 3.2.2 customer is not able to build the app receiving compiler errors related to AssetCryptImpl.java (cannot find symbol and uses unchecked or unsafe operations). During the call we try with different versions from the JDK (1.7 and 1.6) that throw the same error logs. Other apps are being correctly builded with 3.2.1 and failing with 3.2.2, but one app created after the SDK update is not building neither in 3.2.2 or 3.2.1.

Log

[ERROR] :  Failed to compile Java source files:
[ERROR] :  
[ERROR] :  /Users/vamsi.vidala/Documents/Titanium_Studio_Workspace/FRC_Rentals_App/build/android/gen/com/forrent/frmobile/AssetCryptImpl.java:28: cannot find symbol
[ERROR] :  symbol  : variable assets
[ERROR] :  location: class com.forrent.frmobile.AssetCryptImpl
[ERROR] :       Range range = assets.get(path);
[ERROR] :  /Users/vamsi.vidala/Documents/Titanium_Studio_Workspace/FRC_Rentals_App/build/android/gen/com/forrent/frmobile/AssetCryptImpl.java:32: cannot find symbol
[ERROR] :  symbol  : variable assetsBytes
[ERROR] :  location: class com.forrent.frmobile.AssetCryptImpl
[ERROR] :       return new String(filterDataInRange(assetsBytes, range.offset, range.length));
[ERROR] :  Note: /Users/vamsi.vidala/Documents/Titanium_Studio_Workspace/FRC_Rentals_App/build/android/gen/com/forrent/frmobile/AssetCryptImpl.java uses unchecked or unsafe operations.
[ERROR] :  Note: Recompile with -Xlint:unchecked for details.
[ERROR] :  2 errors
[ERROR] Application Installer abnormal process termination. Process exit value was 1

Attachments

FileDateSize
AssetCryptImpl.java2014-03-13T21:42:54.000+00001225
Build.log2014-03-12T19:09:19.000+000051512
Diag.log2014-03-12T19:09:19.000+000027782
Screen Shot 2014-03-14 at 12.59.58 PM.png2014-03-14T19:02:44.000+0000910644
TiConfig.txt2014-03-12T19:09:19.000+00001801
TiInfo.txt2014-03-12T19:09:19.000+000020164

Comments

  1. Ingo Muschenetz 2014-03-13

    Also, can you attach AssetCryptImpl.java?
  2. Radamantis Torres-Lechuga 2014-03-14

    [~ingo] they can not build with any SDK so far, we are waiting the customer to confirm if they have the same issue in different computers, meanwhile, [~egomez] attached the AssetCryptImpl.java file to the ticket.
  3. Ingo Muschenetz 2014-03-14

    So, it looks like they are missing the encrypted resources. See https://github.com/appcelerator/titanium_mobile/blob/f624269bd378d919c464021c06d37e6b3adc66c9/android/templates/build/AssetCryptImpl.java#L26 where they don't have anything there.
  4. Radamantis Torres-Lechuga 2014-03-14

    [~ingo] it's ok if we just copy the entire file in the customer's filesystem?
  5. Radamantis Torres-Lechuga 2014-03-14

    [~ingo] After a fresh install the issue is still there, I'm attaching a screenshot, the only SDK installed it's 3.2.2.GA, any thoughts? we are live now with the customer
  6. Lokesh Choudhary 2014-03-14

    We tried to reproduce the issue but was unable to. The logs in the ticket seem to have been captured when trying to reproduce with different versions of java since the ti.info shows java 1.7.0_51 while studio diagnostic logs shows java 1.6.0 jdk. In the past, we've seen that encryption failures have occurred when the java environment is non-standard. We recommend trying to remove your environment variable for "JAVA_HOME" Environment: Appc Studio : 3.2.1.201402061120 Ti SDK : 3.2.2.GA Mac OSX : 10.8.5 Alloy : 1.3.1 CLI - 3.2.1 Android 4.4.2 - Nexus 5 Android 4.2.2 - Samsung galaxy S4
  7. Chris Barber 2014-03-24

    Sounds like the problem was caused by LiveView. Removing LiveView from the path.hooks appears to have solved the problem.
  8. Lee Morris 2017-03-22

    Closing ticket as invalid with reference to the above comments.

JSON Source