iOS Build trouble after Onesignal service extension installed

Wappler General
1

I have Onesignal running for iOS and Android–receiving push notifications on both platforms. This was was the bare bones installation (no optional steps were performed.)

I then moved to install a onesignal extension for rich push messages. However, after following the Onesignal instructions for iOS Service Extension Wappler can no longer build/archive the project.

My workaround is to open the WORKSPACE in xcode, rather than the PROJECT, as building using the workspace in xcode succeeds, while the project does not. This is supported by the following note on the iOS onesignal install docs:

Make sure to always open the workspace from now on. You can also do this automatically by running xed . from the root of your project.

So it would seem that now that this extension (which is working by the way) is installed, Wappler should be performing the build on the workspace instead of project.

@George @Anybody thoughts on this?

2

What build errors do you get exactly Ken?

3

hello @mebeingken ,
Were you able to publish this project in the app store using one signal? Because we had a lot of problems.

4

This is what is coming out of Wappler...

** ARCHIVE FAILED **


The following build commands failed:
        Ld /Users/pauka/Library/Developer/Xcode/DerivedData/MealPro-eydlhnotnkhvdvgyosphtguerlpx/Build/Intermediates.noindex/ArchiveIntermediates/MealPro/IntermediateBuildFilesPath/MealPro.build/Debug-iphoneos/OneSignalNotificationServiceExtension.build/Objects-normal/arm64/Binary/OneSignalNotificationServiceExtension normal arm64
(1 failure)
xcodebuild: Command failed with exit code 65
Error building your Cordova Project for ios!

And this from xcode:

Screen Shot 2021-11-12 at 7.13.52 AM
Screen Shot 2021-11-12 at 7.13.52 AM922×312 40.5 KB

If I remove the onesignal target, it all goes back to normal...basic notifications working.

For this project, I've gone through to testflight and no issues. For a previous project, it went all the way through review and publishing so never experienced any issues for both ios and android.

5

Just to close the loop on this for when I come back and look for this problem again!

I have Wappler building successfully when the Onesignal service extension is included.

The actual error was being masked but ultimately it came down to mismatches on build versions and deployment target versions across the main app and the onesignal extension. Once aligned, Wappler builds properly again.

I still open the workspace in xcode, rather than the project in order to perform the archive and upload the app.

1 Like