[TIMOB-24045] Android: App launches successfully but errors and warnings show in console log for Samsung devices
GitHub Issue | n/a |
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2019-08-19T20:00:33.000+0000 |
Affected Version/s | Release 6.0.0 |
Fix Version/s | n/a |
Components | Android |
Labels | qe-6.0.0 |
Reporter | Lee Morris |
Assignee | Alan Hutton |
Created | 2016-10-17T20:59:32.000+0000 |
Updated | 2019-08-19T20:00:33.000+0000 |
Description
Steps to reproduce:
1. Create default alloy app in Studio.
2. Build for Samsung device. (Ran on Samsung Galaxy S4 running android 4.4.4 and Galaxy Note II running android 4.3)
Actual Result:
1. App launches successfully.
2. But we see build errors in the console log.
Attached are the log files for the ticket.
Expected Result:
1. Should not see any errors in the console log.
Attachments
[~lmorris] As far as I can tell after looking at the source code where appropriate and after visiting [google issue tracking](https://code.google.com/p/android/issues/detail?id=198567) this is to be expected. When code is compiled for API 23 but is deployed on API 19, these methods will be referenced. In the titanium android source code, there are guards that check if current build version is 23 or above otherwise permission methods e.g. checkSelfPermission are not executed. "this is normal, when you compile your code against 23 but deploy on 19, the IR will add references to methods that were added between 19 and 23." - quoted from [google issue tracking](https://code.google.com/p/android/issues/detail?id=198567) referenced from [dalvikvm virtual method error](http://stackoverflow.com/questions/36874821/how-to-resolve-this-error-vfy-unable-to-resolve-virtual-method)
[~fmerzadyan] Putting this out of 6.1.0 for now. Please let me know if you see crashes or an increased number of reports regarding this.
Closing issue as “Cannot Reproduce”. Out of date with our current release (8.1.0.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please add a comment, and include code that demonstrates/reproduces the issue.