Affects Version/s: None
Fix Version/s: Release 7.5.0
Version of the APM we're using is 3.1.0 for both Android and iOS
Name = Mac OS X
Version = 10.13.3
Architecture = 64bit
- CPUs = 8
Memory = 16.0GB
Node.js Version = 6.11.5
npm Version = 3.10.10
CLI Version = 5.0.14
node-appc Version = 0.2.41
Version = 7.1.0Version of the APM we're using is 3.1.0 for both Android and iOS Operating System Name = Mac OS X Version = 10.13.3 Architecture = 64bit CPUs = 8 Memory = 16.0GB Node.js Node.js Version = 6.11.5 npm Version = 3.10.10 Titanium CLI CLI Version = 5.0.14 node-appc Version = 0.2.41 Titanium SDKs 7.1.0.GA Version = 7.1.0
- CPUs = 8
Sprint:2018 Sprint 09 SDK, 2018 Sprint 10 SDK, 2018 Sprint 11 SDK, 2018 Sprint 12 SDK, 2018 Sprint 13 SDK, 2018 Sprint 14 SDK, 2018 Sprint 15 SDK, 2018 Sprint 16 SDK, 2016 Sprint 17 SDK, 2018 Sprint 18 SDK, 2018 Sprint 19 SDK
This however, has only been tested in simulators/emulators.
It was also tested with Ti SDK 7.x and 6.x. In both cases new Error seems to be broken in Android, but working in iOS.
Steps to reproduce:
1) Take a look at index.js and see how we're trying to instantiate 2 Error objects, then printing them in the console.
2) Run the application in Android (we've been using emulators with Android 6.0 and 7.1.1)
3) When the application launches look at the console. The printed logs will be empty objects:
4) Re-run the app in iOS
5) Observe the console output and how actual error objects will be printed: