Why are you asking this here? Apple doesn't run the Google Play Store.

Report it at feedbackassistant.apple.com.

Where's the crash? What's RenameSheet look like? Do you need to assign nil in var name: String? = nil?

The reason the Mail app opens is because of privacy. No app should be able to send an email without any interaction with the user. To get around this, why not use a PHP script on a server under your control? POST the relevant encrypted information to the script, and let the script send the email using the servers mail command.

Yeah, @jcgoforth, I see what you're saying, but even if I remove the seconds the timers get hours out of sync, i.e. "29:17" (29 hours 17 mins). With a timeline entry every hour - even if were a few minutes out in refreshing it - it should calculate the right time, and never be more than 24 hours. I raised a request to Apple to have proper formatting in timers, and make them more suitable for widgets, but it's fallen on deaf ears.

https://developer.apple.com/download/all/?q=xcode

This doesn't seem like a Developer Forums problem, to me. These are the Developer Forums, where developers ask each other for hints and tips on coding. Your question is more of a support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

I've added a selected tab bar item as a @State var. Such vars should be private because they should only be modified within their own View. Also, you only really need to change the selection within the .onTapGesture because the view will take its data from the change you made, i.e. the image color is set by the value of selected. class MainViewManager: ObservableObject{ @Published var tabbarStatus: TabbarStatus = .homeView enum TabbarStatus: CaseIterable { case homeView case articsPage case profile var icon: String { switch self { case .homeView: return "house" case .articsPage: return "person.2" case .profile: return "person.crop.circle" } } } } struct MainTabbar: View { @EnvironmentObject var vm: MainViewManager @State private var selected: MainViewManager.TabbarStatus = .homeView var body: some View { HStack { ForEach(MainViewManager.TabbarStatus.allCases, id: \.self) { tabbarItem in Image(systemName: tabbarItem.icon) .foregroundStyle(tabbarItem == selected ? Color.accentColor : .gray) .onTapGesture { selected = tabbarItem } if(tabbarItem != .profile) { Spacer() } } } .padding(.horizontal, 30) .padding(.all) .frame(maxHeight: .infinity, alignment: .bottom) .background(Color.white) } } #Preview { MainTabbar() }

This looks like something you should debug yourselves. Have a device on iOS 16.6.x and store the relevant data in the defaults. When the OS is updated to 16.7.2, see if the data is still there. If not, determine why the data isn't there any more. An OS update shouldn't affect data stored in an app's sandbox. (Also, please don't use random tags for your post. This has nothing to do with App Store, Entitlements and Xcode. By using the wrong tags you're actually making the use of tags absolutely pointless. If I'm searching for posts tagged with Xcode and yours comes up, then it's just noise.)

These are the Developer Forums, where developers ask each other for hints and tips on coding. Your question is more of a support one, so I'd suggest you ask it over at the Apple Support Forums, or even get in touch with the developer of the app, i.e. Meta. This isn't an Apple issue, and it's certainly not an issue someone who develops for Apple software is going to fix. Thanks.

These are the Developer Forums, where developers ask each other for hints and tips on coding. Your question is more of a support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks. Also, please don't use unrelated tags for posts. This has nothing to do with the framework Core Audio.

These are the Developer Forums, where developers ask each other for hints and tips on coding. Your question is more of a support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks. If you hate the sounds so much, give Apple some feedback via this link.

These are the Developer Forums, where developers ask each other for hints and tips on coding. Your question is more of a support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks. Send Apple some feedback here.

Given this works in other places in the app, it's more than likely you've done something wrong - and it's not Apple's fault. Remove everything you don't need from that broken bit until it works. Since you won't post any code we can't help you to see where you're going wrong. Sorry.

You've posted this to the Developer Forums, which is where developers - not Apple's developers - ask questions about how to fix something in their code. Your feedback is highly unlikely to get to Apple if you post here. It's like going to a mechanic to complain about the condition of the roads. I suggest you send Apple some feedback directly here. Thanks.