search

paullangtree / analytics-issues

Automatically exported from code.google.com/p/analytics-issues
2 stars 0 forks source link

Crash running unit tests on viewDidLoad: in [UIViewController(TAGAutoEventTracking) TAGManager_viewDidAppear:] using XCode 7.1 #772

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Name of affected component: Mobile Tracking

Name of related library and version, if applicable (e.g. Android, iOS,
Snippets, etc.): iOS, Xcode 7.x, GoogleTagManager 3.12.1 (Cocoapod), Cocoapods 
0.39 or 0.38 (both affected)

Issue summary:
Crash running unit tests on viewDidLoad: in 
[UIViewController(TAGAutoEventTracking) TAGManager_viewDidAppear:] using XCode 
7.1

Steps to reproduce issue:
1. Clone our test project https://github.com/beatrupp/TagManagerCrash
2. Run "pod install"
3. Open TagManagerCrash2.xcworkspace
4. Run unit test target in XCode 7.1 on a simulator (e.g. iPhone 6s plus)

Expected output:
The unit tests should pass since they don't even assert anything.

Actual results:
The unit test "testExample" crashes at the last line with a EXC_BAD_ACCESS

Notes:
Debug output from log:
15:21:37.166 TagManagerCrash2[19771:6691704] 
_XCT_testBundleReadyWithProtocolVersion:minimumVersion: reply received
15:21:37.170 TagManagerCrash2[19771:6691703] 
_IDE_startExecutingTestPlanWithProtocolVersion:16
Test Suite 'All tests' started at 2015-11-02 15:21:37.194
Test Suite 'TagManagerCrash2Tests.xctest' started at 2015-11-02 15:21:37.194
Test Suite 'TagManagerCrash2Tests' started at 2015-11-02 15:21:37.194
Test Case '-[TagManagerCrash2Tests testExample]' started.
warning: could not load any Objective-C class information. This will 
significantly reduce the quality of type information available.

Original issue reported on code.google.com by beat.r...@westwing.de on 2 Nov 2015 at 2:32

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Even I am facing this issue. It is crashing while running the unit test 
scripts. Any solution found to fix this?

Original comment by jithuna...@gmail.com on 9 Nov 2015 at 11:43

GoogleCodeExporter commented 8 years ago 
We are aware of this issue with the unit tests and it will be addressed in the 
next release.

Original comment by mcoh...@google.com on 11 Nov 2015 at 11:14

GoogleCodeExporter commented 8 years ago 
Thanks for confirming. Any tentative ETA of the next release?

Original comment by jithuna...@gmail.com on 16 Nov 2015 at 12:49