iOS Question Problems with BuildServer

marcick

marcick

Well-Known Member
Licensed User
Longtime User
After years of using the Hosted Builder, I bought a Mac and installed everything needed for the local Build Server.
A basic project works, but my main project shows several compilation errors like the ones below.


Are there any additional steps or extra components I need to install (for example Firebase), or should the Build Server package already include everything required?

If I check inside the folder Lib/Firebase I see the files that the log says "missing or invalid"
p.s. I have downloaded and unzipped from the Mac.

B4X: 
error: The signature of “nanopb.xcframework” cannot be verified.
    note: A sealed resource is missing or invalid
    note: /Users/eb/Desktop/B4iBuildServer1000/Libs/Extra/Firebase/nanopb.xcframework: a sealed resource is missing or invalid
file added: /Users/eb/Desktop/B4iBuildServer1000/Libs/Extra/Firebase/nanopb.xcframework/macos-arm64_x86_64/nanopb.framework/Resources/nanopb_Privacy.bundle/Contents/Resources/PrivacyInfo.xcprivacy
file added: /Users/eb/Desktop/B4iBuildServer1000/Libs/Extra/Firebase/nanopb.xcframework/macos-arm64_x86_64/nanopb.framework/Resources/nanopb_Privacy.bundle/Contents/Info.plist
file added: /Users/eb/Desktop/B4iBuildServer1000/Libs/Extra/Firebase/nanopb.xcframework/macos-arm64_x86_64/nanopb.framework/Resources/Info.plist
file added: /Users/eb/Desktop/B4iBuildServer1000/Libs/Extra/Firebase/nanopb.xcframework/macos-arm64_x86_64/nanopb.framework/Versions/Current/Resources/nanopb_Privacy.bundle/Contents/Resources/PrivacyInfo.xcprivacy
file added: /Users/eb/Desktop/B4iBuildServer1000/Libs/Extra/Firebase/nanopb.xcframework/macos-arm64_x86_64/nanopb.framework/Versions/Current/Resources/nanopb_Privacy.bundle/Contents/Info.plist
file added: /Users/eb/Desktop/B4iBuildServer1000/Libs/Extra/Firebase/nanopb.xcframework/macos-arm64_x86_64/nanopb.framework/Versions/Current/Resources/Info.plist
 
Sort by date Sort by votes
Erel

Erel

B4X founder
Staff member
Licensed User
Longtime User
This error means that the signature of this framework doesn't match the framework content. It can happen when the builder package was unpacked in a way that broke something like a soft link.

Download the zip to your mac directly and open it with Finder. If it doesn't work then download Firebase from here:

And replace the problematic framework.
 
Upvote 0
marcick

marcick

Well-Known Member
Licensed User
Longtime User
Yes, I performed all the steps directly on the newly purchased Mac Mini M4 running macOS 26.1.
When downloading with Safari, the file appears already unzipped in the Downloads folder.
I repeated everything from scratch without success.


I manually downloaded Firebase from the link you provided (also using Safari) and copied the entire contents of the Firebase folder into B4iBuildServer/Libs/Extra/Firebase, but I’m still getting the same error.
 
Last edited:
Upvote 0
marcick

marcick

Well-Known Member
Licensed User
Longtime User
sorry but no success. Tried unzipping with finder and also with terminal using "ditto -xk B4iBuildServer.zip B4iBuildServer"
The first compile error I see is always this

B4X: 
error: The signature of “nanopb.xcframework” cannot be verified.
    note: A sealed resource is missing or invalid
    note: /Users/eb/Desktop/B4iBuildServer/Libs/Extra/Firebase/nanopb.xcframework: a sealed resource is missing or invalid
 
Upvote 0
marcick

marcick

Well-Known Member
Licensed User
Longtime User
I don’t know what to say. I bought it new the day before yesterday, turned it on, updated to macOS 26.1, installed the Java SDK and the Build Server. Nothing else.
Could it be caused by something not properly updated on the Windows PC where B4i is running?
 
Upvote 0
Erel

Erel

B4X founder
Staff member
Licensed User
Longtime User
marcick said:
Could it be caused by something not properly updated on the Windows PC where B4i is running?
Click to expand...
No. It is not related to the Windows machine.

Another thing that you can try is to delete the _CodeSignature folder that is inside the framework. It will cause Xcode to skip the signature verification.
 
Upvote 0
marcick

marcick

Well-Known Member
Licensed User
Longtime User
Thanks, but unfortunately, it didn’t help removing that folder …
i will try to reinstall B4i 8.90 and its BuildServer but I feel troubles are with MacOs26
 
Upvote 0
marcick

marcick

Well-Known Member
Licensed User
Longtime User
Hi, I finally managed to solve this issue with MacMini M4 with MacOS26.1 Tahoe (I don't know if it's the same with other Mac or with Sequoia).
Just to clarify: the solution was exactly what Erel suggested (downloading Firebase and removing the signatures).
My problem was that I wasn’t doing those steps correctly, so the frameworks weren’t in a valid state.

Here is what actually worked:

1) BuildServer unzip issue (missing symlinks)
Even though I unzipped the BuildServer with all precautions (Safari auto-unzip disabled, unzipping from Terminal, avoiding Desktop/iCloud folders), the frameworks inside Libs/Extra still didn’t contain the proper symlinks.
ls -l inside nanopb.xcframework showed normal folders instead of the expected symbolic links (Headers -> Versions/Current/Headers, etc.).
So the Firebase frameworks packaged in the BuildServer were not correct.

2) Downloaded the official Firebase Apple SDK again

https://firebase.google.com/download/ios#integrate-manually

This time I completely replaced the folder B4iBuildServer/Libs/Extra/Firebase with the fresh one from the ZIP.
This was one of the steps I had not done correctly before.
Now, ls -l inside nanopb.xcframework correctly show the symlink:

B4X: 
eb@Mac-mini-di-MiniLab nanopb.framework % ls -l             
total 0
lrwxr-xr-x  1 eb  staff   24 24 nov 10:10 Headers -> Versions/Current/Headers
lrwxr-xr-x  1 eb  staff   24 24 nov 10:10 Modules -> Versions/Current/Modules
lrwxr-xr-x  1 eb  staff   23 24 nov 10:10 nanopb -> Versions/Current/nanopb
lrwxr-xr-x  1 eb  staff   26 24 nov 10:10 Resources -> Versions/Current/Resources
drwxr-xr-x@ 4 eb  staff  128  5 nov 06:37 Versions

3) Removed all existing code signatures
Before, I had removed only some signatures.
This time I removed all _CodeSignature folders recursively using terminal:

B4X: 
cd ~/B4iBuildServer/Libs/Extra/Firebase
find . -name "_CodeSignature" -type d -exec rm -rf {} +

After doing the process correctly the project compiled successfully.
Thanks :)
 
Upvote 0
marcick

marcick

Well-Known Member
Licensed User
Longtime User
I understand, and I’m not very comfortable with the situation (also I was thinking to not renew the hosted builder next time).
Is there anything else I can try to better understand where the problem is coming from?
If I understand correctly, the contents of my BuildServer folder should be the same as yours and the one used by the Hosted Builder.
Have you had the chance to test a fresh BuildServer installation on a new Mac M4 running Sequoia/Tahoe?
 
Upvote 0
marcick

marcick

Well-Known Member
Licensed User
Longtime User
Thanks.
I even restored the Mac to factory settings through recovery.
It went back to Sequoia (same issue), then I updated to Tahoe (still the same issue).
Of course, it’s possible that I’m missing something or doing some step incorrectly, but I really can’t see where.
Ok, let’s see if anyone else experiences the same problem.
Thanks as always :)
 
Upvote 0
Johan Hormaza

Johan Hormaza

Well-Known Member
Licensed User
Longtime User
I am also filing a bug, my PC is a Mac Mini M4 with macOS Tahoe 26.1 and B4i v10
error: The signature of “nanopb.xcframework” cannot be verified.
note: A sealed resource is missing or invalid
 
Upvote 0
You must log in or register to reply here.
Top