Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SwiftUI Previews in Xcode 14 not working while adding the WindowsAzureMessaging dependency #135

Closed
getangar opened this issue Nov 21, 2022 · 5 comments
Assignees

Comments

@getangar
Copy link

Describe the bug
Xcode Version 14.1 (14B47b) is unable to generate the SwiftUI Preview when adding WindowsAzureMessaging (v3.1.5) reference from GitHub.

Exception or Stack Trace
HumanReadableSwiftError

SettingsError: noExecutablePath(<IDESwiftPackageStaticLibraryProductBuildable:ObjectIdentifier(0x0000600001a52820):'WindowsAzureMessaging'>)

To Reproduce

  1. Start Xcode Version 14.1 (14B47b)
  2. Load a Project referencing from GitHub the WindowsAzureMessaging library
  3. The project will build without errors
  4. Open a fire containing a View
  5. The SwiftUI preview fails with error

Expected behavior
I expect to see the preview of my SwiftUI view

Screenshots
Xcode

Setup (please complete the following information):

  • OS: macOS Ventura 13.0.1 (22A400)
  • IDE : Xcode Version 14.1 (14B47b)
  • WindowsAzureMessaging 3.1.5

Additional context
The issue I face seems to be similar to this: microsoft/appcenter-sdk-apple#2433

@menteValidus
Copy link

Same problem happened with AppCenter and they fixed it. Hope these links will help to fix this problem.

@menteValidus
Copy link

I'm really blind and didn't notice existing PR. If someone wants a quick fix of this problem before Azure team will merge it just replace your azure dependency with https://github.com/rafaelcalunga/azure-notificationhubs-ios url and choose main branch.

@brannon brannon self-assigned this Jan 23, 2023
@brannon
Copy link
Collaborator

brannon commented Feb 8, 2023

Thanks @getangar and @menteValidus for the bug report. I added a comment to the related PR and was hoping you'd be willing to comment on it too:

#134 (comment)

The TL;DR is: it looks like this has been resolved in Xcode 14.2. Could either of you confirm that is the case?

@rafaelcalunga
Copy link

Xcode 14.2 (14C18) solved this issue for my apps

@brannon
Copy link
Collaborator

brannon commented Feb 9, 2023

Thanks for confirming @rafaelcalunga . I'm going to close this issue, since it was caused by a bug in Xcode 14 and has been fixed in Xcode 14.2.

@brannon brannon closed this as not planned Won't fix, can't repro, duplicate, stale Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants