All geek questions in one place

GoogleSignIn iOS system missing Bitcode support

I would love to enable Bitcode support for my iOS project, but I'm using the Google Sign In framework, and it looks like they STILL did not add Bitcode support to the library.

It seems that I can not find any information on whether this will happen soon or they talk a lot about how other developers require this feature ... Am I a minority? Does anyone else not use the Google Sign In framework on iOS or just don't want to use the bitcode?

I would remove the Google Sign In framework because it was nothing but a problem for me, but I'm afraid that 7% of my users have signed up for Google Sign In, so now I'm stuck with it.

I use containers:

pod 'GoogleSignIn' pod 'GoogleAnalytics'

GoogleAnalytics seems to be fine now and supports BitCode, but the GoogleSignIn structure still gives errors when enabling Bitcode, for example:

... Beans / GoogleAuthUtilities / Libraries / libGTMOAuth2_external.a (GTMOAuth2Authentication.o) "does not contain bit code. You must rebuild it with the bit code turned on (Xcode Setup ENABLE_BITCODE), get the updated library from the provider, or disable the bit code for this purpose for arm64 architecture

+5
source share
2 answers

Yes, it looks like the Sign In library does not currently support BitCode. But you can always disable it, since the bitcode is optional, as Apple says in its notes:

For iOS applications, the bitcode is standard, but optional. If you provide a bitcode, all applications and frameworks in the application bundle must include a bitcode. WatchOS applications require a bitcode.

So you just need to disable it:

  • Choose your goal.
  • Go to build settings.
  • Search for "bit code".
  • Change the Enable Bitcode option to None.

Xcode project

I am.

+2
source

Logging in to Google v 3.0.0 now supports BitCode!

https://developers.google.com/identity/sign-in/ios/release

0
source

Source: https://habr.com/ru/post/1243246/

More articles:


All Articles