Neil Rohan Member Licensed User Longtime User Feb 14, 2026 #1 The forum has an old thread that reports problems with the Firebase frameworks included in the latest Buildserver. The error message was "The signature of “nanopb.xcframework” cannot be verified. note: A sealed resource is missing or invalid". The thread alluded to a rather involved process which involved downloading the firebase library directly from google and overwrite the files that came with the Buildserver. A suggestion was made to publish a corrected buildserver. Erel commented "I guess that this issue will eventually be resolved." Has it been resolved or is the only recourse to overwrite libraries in Buildserver?
The forum has an old thread that reports problems with the Firebase frameworks included in the latest Buildserver. The error message was "The signature of “nanopb.xcframework” cannot be verified. note: A sealed resource is missing or invalid". The thread alluded to a rather involved process which involved downloading the firebase library directly from google and overwrite the files that came with the Buildserver. A suggestion was made to publish a corrected buildserver. Erel commented "I guess that this issue will eventually be resolved." Has it been resolved or is the only recourse to overwrite libraries in Buildserver?
Solution Neil Rohan Feb 15, 2026 Erel said: The reason for this issue isn't clear. A not too difficult workaround is to delete the _CodeSignature folders. Click to expand... Thanks. Will do.
Erel said: The reason for this issue isn't clear. A not too difficult workaround is to delete the _CodeSignature folders. Click to expand... Thanks. Will do.
Erel B4X founder Staff member Licensed User Longtime User Feb 15, 2026 #2 The reason for this issue isn't clear. A not too difficult workaround is to delete the _CodeSignature folders. Upvote 0
The reason for this issue isn't clear. A not too difficult workaround is to delete the _CodeSignature folders.
Neil Rohan Member Licensed User Longtime User Feb 15, 2026 #3 Erel said: The reason for this issue isn't clear. A not too difficult workaround is to delete the _CodeSignature folders. Click to expand... Thanks. Will do. Upvote 0 Solution
Erel said: The reason for this issue isn't clear. A not too difficult workaround is to delete the _CodeSignature folders. Click to expand... Thanks. Will do.
