---------------------------------------------------------------------------
NOTE: This issue tracking system is for Google Analytics developer products
only.
If you are not a developer/programmer visit:
http://www.google.com/analytics/support.html
---------------------------------------------------------------------------
Name of affected component: Mobile Tracking
Name of related library and version, if applicable (e.g. Android, iOS,
Snippets, etc.): iOS
Issue summary:
When validating/releasing app for distribution to the iOS App Store we get the
warning: "App references non-public selector setTimestamp:". I've searched our
entire codebase and we do not use this method. However, if you grep the
libGoogleAnalyticsServices.a library like so:
grep setTimestamp:
./GoogleAnalyticsServicesiOS_3.08/libGoogleAnalyticsServices.a
There is a match - Binary file
./GoogleAnalyticsServicesiOS_3.08/libGoogleAnalyticsServices.a matches
So far it seems that Apple are not rejecting app submissions because of this
warning but they could start doing so at any moment.
Steps to reproduce issue:
1. Download version 3.08 of the GoogleAnalyticsServices library from
https://developers.google.com/analytics/devguides/collection/ios/resources
2. Run the following grep statement "grep setTimestamp:
./GoogleAnalyticsServicesiOS_3.08/libGoogleAnalyticsServices.a"
Expected output:
What do you expect to see after performing the above steps?
No matches. Library does not reference non-public selector setTimestamp:
Actual results:
What do you actually see after performing the above steps?
"Binary file ./GoogleAnalyticsServicesiOS_3.08/libGoogleAnalyticsServices.a
matches" i.e. the library does reference non-public selector setTimestamp:
Notes:
Provide any additional information which might be useful here. Feel free to
attach screenshots or sample code which demonstrates the issue being
described.
Please find attached screenshot showing validation warning when trying to
submit an iOS app using version 3.08 of the iOS Google Analytics Service library
Original issue reported on code.google.com by tomas.br...@ocado.com on 23 Jul 2014 at 9:53
Original issue reported on code.google.com by
tomas.br...@ocado.com
on 23 Jul 2014 at 9:53Attachments: