Closed GoogleCodeExporter closed 8 years ago
I also needed the BITCODE support in my iOS App.
Original comment by BestC...@gmail.com
on 26 Aug 2015 at 2:27
In XCode 7 Beta 5 I get the following compile error with ENABLE_BITCODE=YES in
build settings.
libGoogleAnalyticsServices.a(TAGDataProvider.o)' does not contain bitcode. You
must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an
updated library from the vendor, or disable bitcode for this target. for
architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Original comment by onche...@gmail.com
on 28 Aug 2015 at 8:20
Ditto
Original comment by neil.s.j...@gmail.com
on 31 Aug 2015 at 6:36
Same error as described by #2
Original comment by vbergae
on 2 Sep 2015 at 6:39
Same issue here with Xcode Version 7.0 beta 6 (7A192o).
Original comment by silentas
on 4 Sep 2015 at 8:48
Gold master is out...
Original comment by RRomanc...@gmail.com
on 10 Sep 2015 at 5:17
Come on, the Xcode 7 GM is out! We need the BITCODE support!
Original comment by valeriolg
on 10 Sep 2015 at 11:52
This is the same as with 64bit support. Somehow it takes ages to rebuild the
library. This is my last project with GA.
Original comment by ed...@cybionic-systems.com
on 10 Sep 2015 at 11:55
Looks like only Google Analytics still doesn't support. Other used analytics
tools like Flurry, Heap, Amazon, Yandex, Fabric are fully support bitcode.
Original comment by kirill.k...@gmail.com
on 10 Sep 2015 at 11:56
Would be nice to have BITCODE support!
Thanks
Original comment by miroslav...@rohlik.cz
on 10 Sep 2015 at 2:16
yep - we need this lib updated!
Original comment by jose.go...@saplinglearning.com
on 10 Sep 2015 at 5:05
Met the same issue. Need bitcode support.
Original comment by derjo...@gmail.com
on 11 Sep 2015 at 1:38
When do you release new version Dev team???
Original comment by ltg...@gmail.com
on 11 Sep 2015 at 3:10
It's both amusing and sad how similar this case is to the 64-bit support. I
believe It took Google months to even respond to the issue, and the support was
eventually added almost a year later. It is abundantly clear that iOS is not a
priority to the Analytics team.
Please note that bitcode support is optional unless you are building watchOS
apps. If you are, I recommend you switch to another analytics platform.
Original comment by mar...@essentia.fi
on 11 Sep 2015 at 6:31
Right, Google is too slow to release new features supported by Apple and give
users better expirience in apps.
Original comment by kirill.k...@gmail.com
on 11 Sep 2015 at 6:35
What is this Google company you speak of... Alphabet Inc right? Yeah this is
the only thing holding us up from doing iOS9 releases.
Original comment by michael....@healthpartners.com
on 11 Sep 2015 at 2:38
Need it too!
Original comment by obr...@gmail.com
on 14 Sep 2015 at 1:34
.... how do i get around this?
Original comment by takombor...@gmail.com
on 14 Sep 2015 at 3:29
workaround...in project settings, build settings, under build options, select
NO for Enable Bitcode. NOTE: this wont work if your app has uses watchOS
Original comment by jose.go...@saplinglearning.com
on 14 Sep 2015 at 3:30
FYI, with the Xcode 7 GM Seed you can turn off bitcode on the phone and enable
it on the watch. This allows the use of Google Analytics API on the phone.
Would be nice to add it to the watch too!
Original comment by ellucian...@gmail.com
on 14 Sep 2015 at 10:51
If bitcode support is added, it will not work with Xcode 6. I'm pretty sure
that's the reason Google is not coming up with bitcode supported lib.
Original comment by gau...@moengage.com
on 15 Sep 2015 at 9:41
Maybe it's a good idea if google made a iOS 8 dynamic framework and switch
bitcode on for the framework. How hard would it be for them add this extra
build target to their project.
Original comment by ed...@cybionic-systems.com
on 15 Sep 2015 at 9:47
Xcode 7.0 now released, please add bitcode support...
Original comment by rock88a@gmail.com
on 17 Sep 2015 at 6:55
I've just update to Xcode 7.0 and getting the same issue. Please update the
Google Analytics Library.
Original comment by lephukha...@gmail.com
on 17 Sep 2015 at 7:45
We need support of bitcode in this lib. It's urgent thing.
Original comment by Yanke...@gmail.com
on 17 Sep 2015 at 8:56
When does it support bitcode? We really need it!
Original comment by junya...@gmail.com
on 18 Sep 2015 at 10:21
Yeah, add bitcode support!
Original comment by matejuk...@gmail.com
on 18 Sep 2015 at 4:25
As usual, its the GA library holding up iOS upgrades. *FacePalm*
Original comment by sanj...@zillow.com
on 18 Sep 2015 at 5:36
Would love to see this ASAP!
Original comment by M.V.Mull...@gmail.com
on 18 Sep 2015 at 11:08
Pls. add this soon
Original comment by vicky.me...@gmail.com
on 21 Sep 2015 at 6:25
Please add it!!!
Original comment by wie...@gmail.com
on 21 Sep 2015 at 4:32
Currently unable to submit an update to the appStore for iOS9 as BITCODE has
not been enabled on the library. What is the ETA to make this happen?
Alternatively, will you provide the libraries as full open source to allow the
community to fix these issues please?
Original comment by Jason.Br...@googlemail.com
on 21 Sep 2015 at 9:47
you can still submit apps if you disable bitcode option in your project, for
now.
Original comment by jose.go...@saplinglearning.com
on 21 Sep 2015 at 9:50
Not necessarily. Xcode has a frustrating code signing bug when a parent app
disables bit code but embedes a watch target that requires bit code to be
enabled. C.f: https://forums.developer.apple.com/thread/10392
I'm trying to update my dependencies to newer builds that support bit code. It
seems Google Analytics is the last dependency that does not support bit code.
Original comment by bran...@acorns.com
on 21 Sep 2015 at 9:52
Unless one wants to submit for watchOS...
P
21. 9. 2015 v 23:50, analytics-issues@googlecode.com:
Original comment by obr...@gmail.com
on 21 Sep 2015 at 11:30
As long as you don't include the google analytics library in your watch target,
you can leave bitcode on for the watch. Then on the phone target turn off
bitcode.
This way you can submit your app which includes watch and analytics in the
phone.
The downside is you can't utilize analytics in watch code and your phone
application can not participate in app thinning.
Original comment by b...@brethansenfamily.com
on 22 Sep 2015 at 4:49
[deleted comment]
Just adding my +1 to the noise. Such a pity that their iOS team is notorious
for their silence. Whilst I love the recommendation for "Not using Google for
Analytics" the companies we work for aren't as progressive. What I plan on
doing is using GA along with something else like MixPanel and try to convince
the business to make the switch once they can see how much better they are. I
think we can all agree that the less iOS libraries from Google your product
relies on the better.
Original comment by danielhg...@gmail.com
on 22 Sep 2015 at 2:46
Come on Google, fix this! I'm dropping google analytics and will roll my own
analytics code for a future app release. EVERY time I want to release a new
version of my app I am delayed by some issue or other with google analytics.
Forget it. My users will no doubt be happy to hear that I'm not farming their
device data for google anymore too! Bonus!
Original comment by i...@myhourz.com
on 24 Sep 2015 at 9:55
How long should we still waiting?!
Original comment by rusya....@gmail.com
on 24 Sep 2015 at 1:15
Google, anything ...
Please provide a new version of Google Analytics with bitcode enabled.
Original comment by milen.ha...@mentormate.com
on 24 Sep 2015 at 1:32
Google PleaaaseHelppp!
Original comment by fabrice....@gmail.com
on 25 Sep 2015 at 11:43
It seems to me obvious that mr. G. is not interested in us: in 3 months they
even did not borther to post any response. I am dropping Goggle Analytics
support from my apps once and forever and I suggest you the same.
Original comment by Janos.To...@gmail.com
on 25 Sep 2015 at 4:36
Is there any news about when this will be fixed?
Original comment by christia...@codecentric.de
on 29 Sep 2015 at 7:31
Original comment by mcoh...@google.com
on 29 Sep 2015 at 3:27
fuck
Original comment by Nikita.A...@gmail.com
on 30 Sep 2015 at 1:52
Uh, no. It should be added. If not, maybe we should drop something else
from our apps.
Original comment by h.bruin...@coolblue.nl
on 30 Sep 2015 at 1:55
Don't hold your breath. Last time there was Google Sign In issue preventing
apps from being accepted in the app store.
(https://code.google.com/p/google-plus-platform/issues/detail?id=900) It took
Google 10 months to fix it. 10 months to fix show stopper that prevented from
using Google's iOS library. 10 months. Only 3 months passed since this issue
was opened.
Original comment by roman.r...@gmail.com
on 30 Sep 2015 at 4:00
As always, Google is quicker in copying Apple than supporting Apple.
I had the impression that Google was the open(source) company. Why just not
make the library opensource.? Is their something we're not allowed to see? Is
Google the Volkswagen of the IT world?
Original comment by ed...@cybionic-systems.com
on 30 Sep 2015 at 4:08
[deleted comment]
Original issue reported on code.google.com by
ellucian...@gmail.com
on 18 Jun 2015 at 3:12