search

alooi14 / analytics-issues

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

iOS SDK: Could results in rejection in review due to 2.23(iCloud Backup) #556

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
---------------------------------------------------------------------------
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 SDK, all versions (confirmed in iOS SDK version 3.0.0 or 
above)

Issue summary:
Using Google Analytics SDK for iOS could results in rejection in review because 
of violation 2.23 (iCloud Backup).

Steps to reproduce issue:
1. Integrate SDK into any iOS app. Settings doesn't matter.
2. Send somewhat large number of events and screenviews.
3. Check out the file attribute and file size of ~/Library/googleanalytics-*, 
especially ~/Library/googleanalytics-v3.sql-wal

Expected output:
Either file size would be always small enough to be ignored by reviewers (less 
than a few KB) or has a com.apple.MobileBackup attribute

Actual results:
Neither of these. ~/Library/googleanalytics-v3.sql-wal can be up to 4MB or so 
(as far as I have experienced) and is not marked as "iCloud Backup Disabled" so 
that reviewers might want to reject apps because of this.

Notes:
This is exactly the reason my app was rejected. They mentioned I had 8MB of 
unnecessary iCloud Backup files in my app and 4MB of them are from Google 
Analytics. I strongly believe this is a bullshit of Apple bureaucratic review 
system but still I believe we should set iCloud Backup disabled by default.

Original issue reported on code.google.com by directio...@gmail.com on 22 Dec 2014 at 5:11

GoogleCodeExporter commented 9 years ago 
Oops, posted in wrong account by accident. Would somebody kindly remove this 
post immediately? I've posted the exact same bug report in my personal account 
as #557.

Original comment by directio...@gmail.com on 22 Dec 2014 at 6:54