I found this: swiftui-lab.com/scrollview-pull-to-refresh
So far, this is the closest I've gotten to a pull to refresh that works. I was able to adapt it for my needs in one project.
That being said, there only seem to be a small handful of examples of people attempting this on their own, none of which work flawlessly. I'm really hoping to see native pull to refresh added simply so we're all doing it in a consistent and preferred manner.
webbguyatwork
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Bourbonnais, IL, United States
Post
Replies
Boosts
Views
Activity
I have several of these types of calls within my app. It's going to look something like this:
private func findSomething(completion: @escaping (Object?) -> Void) {
	loadJsonData(url: URL!) { (data, response, error) in
		if (error != nil) {
			let myObject = Object(<params>) - Or JSON decode here
				completion(myObject)
			}
			else { completion(nil) }
	}
}
Notice there is no return type, only a completion function that you can name whatever you like. Then just call it:
findSomething() { (object) in
	if (object != nil) {
		print(object)
	} else {
		print("Did not find anything")
	}
}
I'm having the same issue. I noticed late in the day yesterday that my simulator was running iOS 14.1 and my device was still on 14.0. I was having pretty good luck in the simulator getting my modals to close, so I updated the phone and it didn't help. Now this morning, the simulator won't close them either. Like you, I've tried both methods as well. It seems to only get stuck once a control on the view becomes first responder and the keyboard is activated. As long as I don't click into a TextView, the view closes just fine all day long. Help!!
I seem to be having some better luck now. While I can't for the life of me explain why it works one way and not the other, here's what I had to do to get a more consistent closing action for my modal view. And doing it this way, the environment presentationMode method works just fine.
@State private var openComposer = false
var body: some View {
	NavigationView {
		ZStack {
			Color("LightGray").edgesIgnoringSafeArea([.all])
			ScrollView {
				VStack {
					<view stuff here>
				}
			}
			.toolbar {
	 ToolbarItem(placement: .navigationBarTrailing) {
	 Button(action: {
	 self.openComposer.toggle()
	 }) {
	 Image(systemName: "ellipsis.bubble.fill")
					}
/*
					NO, NO, NO - Causes problems placed here
					.fullScreenCover(isPresented: $openComposer) {
						ActivityCreatorView()
					}/
	 }
	 }
	 }
	}
	.fullScreenCover(isPresented: $openComposer) {
		ActivityCreatorView()
	}
}
So I guess the trick here is to tie the full screen cover views to the outermost container of the view and not to the buttons that trigger them. Here's wishing you similar luck!
After further research into my issue, I determined it had more to do with the way I was implementing tab item badges. I found some examples on YouTube to implement them over the top of the tab bar, but they seem to be overtaking the entire screen, blocking out my close buttons on the full screen modal. I've since disabled the tab item badges, and that's ultimately what fixed my problem.
@Claude31, I would agree that it makes more sense to have the fullScreenCover attached to the outermost view, in this case my NavigationView. I think that's how I'll do it from now on.