Closed sebastian-foreflight closed 3 years ago
Hi @sebastian-foreflight
Thank you for getting in touch with us and reporting this issue!
We will investigate this problem with using the Xcode 12.5b3 and get back to you once we have an update.
Meanwhile, a small question. Have you had a chance to try this scenario on a stable Xcode version?
We will investigate this problem with using the Xcode 12.5b3 and get back to you once we have an update.
Thank you! Let me know if you have any further questions.
Meanwhile, a small question. Have you had a chance to try this scenario on a stable Xcode version?
Yes, everything builds just fine with Xcode 12.4. I believe this is a new check in Xcode 12.5.
Hi @sebastian-foreflight
I'm sorry for such a delay, just managed to install Xcode12.5b3 😅
Unfortunately I couldn't reproduce the issue following your steps. I installed AppCenter Crashes and Distribute modules using SPM, then included modules in AppDelegate just as you said and was able to successfully run the app on ios simulator (ios 14.5). Tested with both Swift and Objc.
Could you please try to reproduce the issue on an empty project? It would be helpful if you could share a sample as well.
Hi @DmitriyKirakosyan, I will work on a sample project for you.
One thing I should have clarified, this is actually a warning by default, but we, like many other teams have Treat Warnings as Errors
set to Yes
. The default is No
so that might explain why it didn't reproduce when you tried.
Here is a project with Treat Warnings as Errors
set to Yes
that fails to build with 12.5b3 and does build with 12.3
Hi @sebastian-foreflight
Thanks a lot for your demo project. You were right regarding the warnings. I was able to reproduce the issue once I turned this option ON. It is reproducing on your project as well.
Thanks a lot for reporting this issue. I filed a bug on our board and we will fix it according to our priority queue.
Hi @DmitriyKirakosyan
Thanks for letting me know and I'm glad to hear you were able to reproduce the issue. By way of prioritization input, this issue will block us, and likely a number of other teams, from moving to Xcode 12.5, which has a number of improvements we're excited about.
Hi @sebastian-foreflight
Sorry for the delay.
We've merged the fix into develop
. Could you try it out and tell me if it works for you?
We've merged the fix into
develop
. Could you try it out and tell me if it works for you?
Thanks for the fix. I did verify it successfully with the branch so I expect it'll continue to work, but I'll let you know if I see any further issues. From my standpoint this issue can be closed.
I've also noticed that the Xcode 12.5 RC doesn't have this same warning. I'm not sure if the Xcode team intends to re-introduce it later, but for anyone trying to reproduce the issue in the future, note that it's only known to occur in Xcode 12.5b3.
I was suspecting that it was a bug in Xcode beta. Anyways, better to be on the safe side :)
I have begun seeing this issue in my code today. I just so happened to update my Xcode from 12.4 to 12.5 this morning and this same set of build errors started happening. I updated my AppCenter SPM packages from v4.1.0 to v4.1.1 to no avail. Interestingly though, if I pull from the develop branch, the build succeeds.
@WERUreo, the fix is merged but it is not released yet.
The fix has been released in the 4.2.0 version of App Center SDK. Please update App Center to the latest version and let me know if this issue still persists.
Description
Compilation issues when including the SDK with Swift Package Manager and Xcode 12.5b3. The SDK is included in my application using
Repro Steps
@import
statementsDetails
pod --version
)?MSAppCenter.setLogLevel(.verbose)
before your call toMSAppCenter.start(...)
for Swift, or[MSAppCenter setLogLevel:MSLogLevelVerbose]
before[MSAppCenter start: ...]
for Objective C and include the logs here:The compilation errors are:
I believe this is a new error in Xcode 12.5. I've resolved it for packages under my control by adding the headers to the umbrella header.