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

EXC_BAD_ACCESS in SwiftUI in Xcode Beta 7 #7

Open
melgu opened this issue Sep 4, 2019 · 7 comments
Open

EXC_BAD_ACCESS in SwiftUI in Xcode Beta 7 #7

melgu opened this issue Sep 4, 2019 · 7 comments

Comments

@melgu
Copy link

melgu commented Sep 4, 2019

Full error: Thread 1: EXC_BAD_ACCESS (code=1, address=0x9)

The error appears on the marked line:

private struct Observer: View {
	@ObservedObject fileprivate var derived: Lazy
	fileprivate var content: (Derived) -> ChildView

	var body: some View {
>>>>		return self.content(derived.value)
	}
}

I'm on the ImageIOSwift 1.0.0 branch using Xcode 11 Beta 7.
In Xcode 11 Beta 6 it worked. Now it doesn't anymore.

@melgu melgu changed the title EXC_BAD_ACCESS in SwiftUI in new Xcode Beta EXC_BAD_ACCESS in SwiftUI in Xcode Beta 7 Sep 4, 2019
@davbeck
Copy link
Owner

davbeck commented Sep 4, 2019

Hmmm. Is this with the sample app, and if not can you provide an example app or test case that reproduces this? I can’t remember if I last ran tests with beta 6 or 7, but at that time everything seemed to be working.

@melgu
Copy link
Author

melgu commented Sep 4, 2019

The example Mac App crashes as well.

I first noticed it in my TidalSwift App, but yes, the example app crashes with the same error at the same position.

@davbeck
Copy link
Owner

davbeck commented Sep 6, 2019

Gave this a try yesterday on Xcode beta 7, both in the simulator and on a device running 13.1 beta 2. Perhaps something got fixed between beta 1 and 2 of 13.1?

@PatrikTheDev
Copy link
Contributor

The same thing is happening once again with Xcode 11.2, tho it doesn't tell me what's wrong. When I comment out the URLImageSourceView, it works, but once I remove it, I have the issue again. Could you please look into this? @davbeck

@davbeck
Copy link
Owner

davbeck commented Oct 24, 2019

I just gave the sample app another try on Xcode 11.2 beta 2 and it still works for me. If you can provide a sample app that causes the error I can maybe take a look at that.

@reinhardt1053
Copy link

I got the same issue on XCode 11.2.1

@PatrikTheDev
Copy link
Contributor

Solution: either use CocoaPods until it gets fixed or set DEAD_CODE_STRIPPING to YES in your build config file.

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