Post not yet marked as solved
We have a new open source SwiftUI package for the needs, at https://github.com/mobilinked/MbSwiftUIFirstResponder
The SwiftUI style APIs
TextField("Name", text: $name)
.firstResponder(id: FirstResponders.name, firstResponder: $firstResponder, resignableUserOperations: .all)
TextEditor(text: $notes)
.firstResponder(id: FirstResponders.notes, firstResponder: $firstResponder, resignableUserOperations: .all) 2. Option for "tap to resign" for iOS
3. Option for "click to resign", "return key, esc key, ... to resign" for macOS
It almost meets all the needs in the replies.
Post not yet marked as solved
You may need to increase the release number.
Post not yet marked as solved
Similar problem here:
Using @SceneStorage to storage filtering state, sometimes the app crashed when changing the SceneStorage value.
@SceneStorage("filtering-string", defaultValue: "")
var filteringString: String
This variable is used in two views, one for input and one to use it to show a list.
Error message: AttributeGraph precondition failure: setting value during update
Same problem here using Xcode12 beta6
I have created a extension to prevent auto dismiss very easily, just call the way like:
.sheet(isPresented: $presenting) {
ModalContent()
.allowAutoDismiss { false }
}
The code
https://gist.github.com/mobilinked/9b6086b3760bcf1e5432932dad0813c0
Post not yet marked as solved
This bug stoped us to release the first SwiftUI app, and a feedback (FB7599129) has been fired at Feb, 2020.
The problem is that for the language if we need to type multiple keys to input one character, the textfield does not work.
@Apple, would you please help to suggest the solution, the textfield should be very basic I think.
Thanks @JakeShort
Yes, we also think that Apple MAY combine the iOS and macOS (and the app stores) into one at future, and encourage to combine the the iOS, iPadOS and macOS apps together.
Right now, we prefer to developer macOS app NOT using the Catalyst as we want to the app be a real Mac app to use platform-specific capabilities. But with the news about Apple silicon, we have no more idea about Apple's direction - combine all into one or still keeping them be separated. If Apple's direction is to combine them together, we will choose Catalyst.
Post not yet marked as solved
Can anybody help on it?I did not find any other way to know if the opened file is writable except the API to "isWritableFileAtPath", and I did not find any topic related about the file permission in the shared readonly iCloud Drive folder.
Just migrated to the xcode 13.3, the problem backs to the simulator- On the iOS device, it works well - BUT on the simulator, only the first tap works to navigate.
After migrated to Mojave beta 11 and XCode 10 GM, still same problem. @Apple, is it ready for us to submit the app to app store?
Thanks @rich,Yes, remote-validation works.Using remote validation needs addtional investment on the hosting and server side application. My solution is not the remote validation, the app still use local verification, but added more logic to analyze all the transaction data and store the data in safe area (like another copy of receipt) Best, Philip
Thanks,I have no problem to migrate the main app to use the dark mode, the problem is only for the today widget.
Thank @richThe major problem is that after "restore purchased transactions", the receipt in the macOS app bundle will not be updated (checked manually and using code).The code works well on the iOS device (the receipt will be updated correctly)For the macOS app, I have to write code to save the transaction date (monitor by transactionObserver) in safe area, and write code to validate if the purchase expired. This problem was reported at beginging of this year at https://forums.developer.apple.com/message/290288#290288 and a year ago at https://forums.developer.apple.com/message/258440#258440 by other users. I thought I may made a mistake, it's hard to believe it's a bug as it's so important and so basic for the local verification of auto-renewal subscriptions. Thanks,
Thanks PBK,About the logs in my preview:- At 13:35, the user (I as the tester) clicked a button to purchase a product (of cause the app call the store api to do it). After finished, the receipt be updated correctly.*** no problem ***- But before 13: 50, there is no transaction (for renewal) come ("updatedTransactions" not be called). The app has no problem to observe the transactions by calling "SKPaymentQueue.default().add()"*** this is a problem ***- Then at 13: 50, the user (I as the tester) cliked a button to restore the purchases (the app calls the "restoreFinishedTransactions"). You can see in the log, there are 4 transactions received, one is for purchasing, three for renewal. Please pay attention, at the time 13:50, only 15 minutes passed after purchasing, so only 3 renewal transactions received. You see the app receive the transactions correctly, so no warry on the transaction observer*** no problem ***- After "restoreFin..." called, the app will also do the local validating. The receipt was not be updated after "restore..." called (the app get just one record in the receipt which is same as the receipt after purchasing at 13:35). Then I manually check the receipt file in the app bundle, the last modify date is still at 13:35Following the log for the data in the receipt:------------ Receipts and State -------------com.****.monthly (2018-08-20 13:35 --> 2018-08-20 13:40)*** this is a problem ***=========================More1. I did checked (local verification) many times using the code2. And I did checked many times manually (check the last modify time, and file size of the recipt file)The problems are:- "Restoring" does not update the receipt file in the app bundle- "updatedTransactions" calling is not stable for RENEWAL transaction ONLY (sometimes it works, sometimes I need wait very long time, or no any response after a very long time. BTW, I know the 5 times limitation, I just test after purchasing a product)But strangly:- "Refresh" receipt works well- "Purchasing" works well (the receipt will be updated correctly, all transaction be triggered well)From my testing, you may agree:- The app has no problem to deal with 173 error, and the app has no problem to observe transaction- No need to worry about the local verification code, as I also manually check the file last modification time and file size (the major problem is after restoring, the receipt is not be updated, just checking the receipt file last modifiy time is enought).- The "paymentQueue(..., updatedTransactions ...)" and "paymentQueueRestoreCompletedTransactionsFinished" are always called by the app every time after "restoreFinishedTransactions" be called, the problem is that then the receipt file will not be updated (checked by local verification code, and by manual checking the file last modifiy date ...)Thanks much.