Hi,
I want to build an app with using OneSignal plugin but it returns the following error:
-[OSInAppMessageView setupWebViewConstraints] in libplugin_OneSignal.a(OneSignal-armv7-master.o)
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)</result>
ERROR: Builder failed: Undefined symbols for architecture armv7:
Which I built the app few days before and it works fine.
Does anyone know what’s happen?
Thanks
Raymond
raymondwong, thanks for reporting. We missed adding WebKit and UserNotifications iOS frameworks required by a new release of our SDK which now supports In App Messaging. We just added these missing frameworks and it should automatically be pick up by Corona in the next few hours.
the same problem
wait your fix
the problem is actual
@burdin.a.d3 are you seeing this error when building?
“ld: symbol(s) not found for architecture armv7”
If so can you provide the full log?
After we released the fix yesterday I have not been able to reproduce the build issue. We tested with the latest Corona daily 2019.3548 and Xcode 11.2 on an iOS 13.2 device.
The problem is still exist
I’m not sure but I’m using OneSignal v1.15.0
Xcode version 10.3
Here is the log for my build:
<result>ld: warning: object file (/Users/Raymond/Desktop/someapp.app/.build/plugin.OneSignal/libplugin_OneSignal.a(OneSignal.o)) was built for newer iOS version (10.0) than being linked (8.0)
ld: warning: object file (/Users/Raymond/Desktop/someapp.app/.build/plugin.OneSignal/libplugin_OneSignal.a(OneSignalCoronaDelegate.o)) was built for newer iOS version (10.0) than being linked (8.0)
Undefined symbols for architecture armv7:
“___isPlatformVersionAtLeast”, referenced from:
-[OSInAppMessageViewController addConstraintsForMessage] in libplugin_OneSignal.a(OneSignal-armv7-master.o)
-[OSInAppMessageView setupWebViewConstraints] in libplugin_OneSignal.a(OneSignal-armv7-master.o)
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)</result>
Xcode 10.3
we can’t use 11.2 because we have problem with in-app purchases with iap badger plugin
Log:
ERROR: Builder failed: ld: warning: object file (/Users/alexey/Documents/Build Corona Apps/Argonauts.app/.build/plugin.OneSignal/libplugin_OneSignal.a(OneSignal.o)) was built for newer iOS version (10.0) than being linked (8.0)
Nov 08 12:34:05.083 ld: warning: object file (/Users/alexey/Documents/Build Corona Apps/Argonauts.app/.build/plugin.OneSignal/libplugin_OneSignal.a(OneSignalCoronaDelegate.o)) was built for newer iOS version (10.0) than being linked (8.0)
ld: warning: object file (/Users/alexey/Documents/Build Corona Apps/Argonauts.app/.build/plugin.appodeal.beta.base/libplugin_appodeal_base.a(AppodealLibrary.o)) was built for newer iOS version (10.3) than being linked (8.0)
Undefined symbols for architecture armv7:
“___isPlatformVersionAtLeast”, referenced from:
-[OSInAppMessageViewController addConstraintsForMessage] in libplugin_OneSignal.a(OneSignal-armv7-master.o)
-[OSInAppMessageView setupWebViewConstraints] in libplugin_OneSignal.a(OneSignal-armv7-master.o)
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
up
I also want to know when will be the update ready, since my app needs to release a new update soon
There are a number of errors such as “was built for newer iOS version (10.0) than being linked (8.0)” that state that the version of iOS being linked to is too old.
ERROR: Builder failed: ld: warning: object file (/Users/alexey/Documents/Build Corona Apps/Argonauts.app/.build/plugin.OneSignal/libplugin\_OneSignal.a(OneSignal.o)) was built for newer iOS version (10.0) than being linked (8.0) Nov 10 10:59:49.935 ERROR: Builder failed: ld: warning: object file (/Users/alexey/Documents/Build Corona Apps/Lovepix.app/.build/plugin.appodeal.base/Appodeal.framework/Appodeal(Appodeal.o)) was built for newer iOS version (9.0) than being linked (8.0)
It includes OneSignal and a number of other plugins in the log. Can you bump the minimum link version to iOS 10?
If you can build your app with Corona 2019.3509 or older an older version of OneSignal will be used that isn’t linked to iOS 10 as a possible work around.
The OneSignal SDK does support back to iOS 8.0 so we will continue to look into the linker error.
Thanks.
Thank you
Using version 3509 and XCode 10.3 we get the build without errors, but with multiple warnings like this “warning: (armv7) /tmp/bitcode_strip.LJdcF6 unable to open object file: No such file or directory”
Are they critical?
You wrote above that on Xcode 11.2 and iOS 13.2 everything works correctly without errors, I understand correctly?
We’d like to check at the end of the week if that’s the case.
I am not sure what is the driving factor on what Corona picks as the iOS SDK version to link with. We linked the iOS SDK with iOS 10 which was first included in Xcode 8 believe.
I would guess Corona upgraded the iOS version they link with somewhere between the 3510 and 3548. It is possible they choose the link version based on the Xcode version installed but probably only related to the Corona build number.
Hi,
Is there any update on this?
Since I cannot update Xcode right now and I can only use Xcode 10.3 in this moment.
But it is not a good idea that I keep use the Corona version 3509 to build app.
Thanks
Raymond
I have the same issue and have a business app that needs to be published this month. Status please.
I did some additional testing and found the following versions must be used when including OneSignal in your Corona project