react-native-background-geolocation: build failed with linker issues
Your Environment
- Plugin version: 4.0.2
- Platform: iOS or Android
- OS version: 14.4
- Device manufacturer / model: Iphone 11
- React Native version (
react-native - 0.61.5
): - Plugin config
PASTE_YOUR_CODE_HERE
Expected Behavior
application will run normally
Actual Behavior
crash build show error build failed
Context
Debug logs
Showing All Errors Only Undefined symbol: OBJC_IVAR$_DDLogMessage._tag
application will show a build failed error i and i have install pod CocoaLumberjack
- RNBackgroundGeolocation (4.0.2):
- CocoaLumberjack (~> 3.7.0)
i have install the pod and install library sucessfully and do all the steps but build failed
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 32 (20 by maintainers)
@WaseemAhmed645, @ziyaddin
react-native-background-geolocation@4.0.3
is released to npm withCocoaLumberjack
pinned @3.7.0
My release build with same just finished archiving right now and is uploading to TestFlight, back in business!
It seems
CocoaLumberjack@3.7.1
deprecated a_tag
property that I’m using, but what they really meant was they removed it.TSLocationManager
’sPodfile.lock
was pinned atCocoaLumberjack@3.7.0
. Doing apod update CocoaLumberjack
, now I see the error inTSLocationManager
src. That’s a crappy thing to throw down into a point-release.yeah, I use myself as a crash test dummy with a sort of daily update to see what bitrot (and fun) happened with updates overnight, in order to catch the falling knives before the users file bug reports in react-native-firebase etc, so makes sense I would see this immediately. Unfortunate it bit @WaseemAhmed645 and @ziyaddin as well.
The change was actually from October, just appears they were slow to release it. I commented here: https://github.com/CocoaLumberjack/CocoaLumberjack/pull/1177#issuecomment-816273495
Pinning the dependency in my Podfile works, via this line, and I guess you just have to kill the tilde in the podspec for the dep here as they’re not semver safe?
And oops: I left my
npm publish
hanging last night waiting for me to enter the OTP Code.4.0.3 was published just now to npm.
private.
3.7.1
was released yesterday. I think we pin to3.7.0
for now.I made contact with the author of CocoaLumberjack. He has released
3.7.2
, re-introducing the removed_tag
property.@WaseemAhmed645 License key is needed only for Android, not iOS.
that git ref yarn installs correctly, pod installs as ‘4.0.4’, I removed my CocoaLumberjack version pin from above prior and then did a
pod outdated
and it correctly showed 3.7.1 of CocaLumberjack was available but not accessible due to version restrictions from the Podfile (oh and it builds of course, that’s important…)Just to make sure I deleted Podfile.lock, re-did pod install and still got CocoaLumberjack 3.7.0, with the Podfile.lock expressing the specific 3.7.0 version as dependent from here
Looks all good
This has happened to me a few times recently with other projects.
npx react-native-clean-project
(and specifically clearing the Xcode build cache, whether that is in ios/build or ~/Library/big/xcode/path/to/DerivedData - which react-native-clean-project takes care of)