Post not yet marked as solved
I'm also encountering this.
Feedback: FB13554487, including logs and project source, and a link to the failing build.
Thanks.
Post not yet marked as solved
I'm not sure what to make of DocumentGroup. It seems like the way we're supposed to create a document-based SwiftUI app, but it's missing major pieces of functionality.
For example, there's no way to do state restoration. No way to run tests that create and open documents. No clear way to present first-run UI or let the user pick a document type to create.
Is everyone rolling their own alternative or how are people handling this?
Post not yet marked as solved
So what's the solution for using MVVM in a setup where you're using EnvironmentObject to pass in access to the model?
I'm thinking of something like Core Data where you can use an EnvironmentObject to pass in an NSManagedObjectContext. You can't create an @EnvironmentObject ViewModel in init because the EnvironmentObject isn't set yet. And the EnvironmentObject property's didSet doesn't fire so you can't do it there.
Creating the ViewModel in onAppear works but seems a bit clumsy. Is that the best way to do this?
Post not yet marked as solved
So, no advice on this?The documentation is incorrect, and as noted on the documentation pages, is no longer being updated. Is there a newer endpoint we can use or some other way of verifying receipts?
Post not yet marked as solved
I'm not at the point of getting receipts from the live environment, but I've seen examples that show the expires_date in a different format. For example, here and here.These posts show a receipt with an expires_date field in this format:"expires_date":"2016-12-31 17:05:24 Etc/GMT",I'm lookiing for guidance on how to parse this field. Try as milliseconds and if that fails, try as this format, and if that fails try RFC 3339? I don't want to find out when I deploy the live app that the date is coming back in a format I was unable to test.Thanks
