You may need to implement a sheet by yourself. I found a third-party package BottomSheet which might be what you want. — WindowsMEMZ @ Darock Studio let myEmail = "memz" + "1" + "@" + "darock.top"

1.可以从我的 APP 跳转到 iOS 的照片并且定位到选择的照片/视频吗？ (1. Is it able to open Photos app from my app and locate to selected photos/videos?) No, you can't. 2.PHPickerViewController 没有全选的功能，...... 我是可以通过代码自建picker 来调用到这些合集里的内容来全选添加吗 (2. Seems like there's no Select All feature in PHPickerViewController, ... Can I build a picker by myself to allow users select all photos in a group?) Selecting all photos is not allowed for App Store submission according to App Review Guidelines 5.1.2(v): (v) Do not contact people using information collected via a user’s Contacts or Photos, except at the explicit initiative of that user on an individualized basis; do not include a Select All option or default the selection of all contacts. You must provide the user with a clear description of how the message will appear to the recipient before sending it (e.g. What will the message say? Who will appear to be the sender?). However, if you don't plan to distribute your app on App Store, you can request full access to users' photo library and build your self photos picker, which is not suggested. — WindowsMEMZ @ Darock Studio let myEmail = "memz" + "1" + "@" + "darock.top"

It may be a problem of HomeBrew. Have you tried to upgrade your HomeBrew? — WindowsMEMZ @ Darock Studio let myEmail = "memz" + "1" + "@" + "darock.top"

Have you tried this? It works for me: prefs:root=General&path=SOFTWARE_UPDATE_LINK — WindowsMEMZ @ Darock Studio let myEmail = "memz" + "1" + "@" + "darock.top"

You can use List with an onMove modifier: struct MyView: View { @State var data = [1, 2, 3, 4, 5] var body: some View { List { ForEach(0..<data.count, id: \.self) { i in Text(String(data[i])) } .onMove { source, destination in data.move(fromOffsets: source, toOffset: destination) } } } } — WindowsMEMZ @ Darock Studio let myEmail = "memz" + "1" + "@" + "darock.top"

I believe this is a bug because I can reproduce it on Swift Playgrounds 4.6 but not on 4.5.x. You can file a feedback in Feedback Assistant. Take a look at the forums post: Bug Reporting: How and Why?