That did it! I... never would've guessed that, from the error.
Post not yet marked as solved
Hey, greay, did you ever find a solution for your problem? I'm having a similar problem with an app I'm working on where I have a one-and-done binding that functions as expected the first time, but then doesn't fire again upon changes. Any guidance would be greatly appreciated. :) No, I ended up moving completely away from SwiftUI because I need to support older versions of macOS.
Post not yet marked as solved
I should add/clarify that both of these apps are already for sale on the store. We are NOT trying to change anything under "App Information" – like the localizable name. We want that to stay as-is. All we're trying to do now is add localized copy for the stuff in the update: What's new, promotional text, description, etc.
Post not yet marked as solved
Hmm, ok, that suggests to me that the problem isn't in this construction itself, but something further up.As I hinted, but should've made more explicit, the [Check] is a property on another struct. The larger structure has some pretty deeply-nested subviews, too much to put in a forum post, so I was hoping this small snippet would be enough to highlight what was going wrong. It wasn't – but since this works, I'm thinking I might be able to slowly grow out from this & poinpoint the problem.
Post not yet marked as solved
It's in an existing application, so the change actually breaks some functionality.In the app on the store, certain on-screen buttons are disabled when the keyboard appears. They're re-enabled when you press submit, dismissing the keyboard. Since the notifications are no longer sent, those buttons never get re-enabled.Basically, the text entry is a modal operation, and the existing code relies on those notifications to exit that mode. Might not be the best design, but I didn't write the original code.
Post not yet marked as solved
But it's not always visible. I would still expect it to send the will/did show notifications when it appears. And send the will/did hide notifications when it's dismissed. If this is in fact by design, it should be documented.Having to check whether the starting/ending frame's bounds is zero seems incredibly backwards to me.
So, I never did actually figure this out. I eventually managed to work around it, but the app still asks me to log into ... some account? every time I launch. Still just says "Enter the password for ."I'm not convinced that there being no way to clear Key-Value data is a good thing, because having that would make my life a *whole* lot easier. Especially since there's no iCloud sandbox, having this data persist invisibly makes testing & troubleshooting that much more difficult. Having a simple way to ensure a clean slate would be grand.
So, yeah. I'm blocked.This app *does* use IAP, so I definitely need to be able to log into a sandbox account. But I'm trying to add iCloud sync for some saved settings & such, so I guess I need to use my normal iCloud account for that. This is using *iCloud Key-Value Store*, which I'm led to believe is somehow different from CloudKit, though I'm still not 100% clear on the distinction between all the different iCloud approaches. So I have 3 questions, now.1: is it possible to use a Sandbox account for IAP at the same time as iCloud Key-Value Store? It seems like it should be, since they're separate settings.2: what account is it asking me to log into on launch, and why can't I login?3: Is there *any* way outside of adding a debug setting in the app to clear the Key-Value Store? Even though the data persists across deleting & reinstalling, it doesn't show up in iCloud's "Manage Storage"
Oh. It didn't occur to me that they'd be different. And the alert doesn't tell me what account I'm supposed to be signing in to. It's a shame there isn't a way to use sandbox accounts for CloudKit, as well. It would make my life *a lot* easier...Actually, it's not accepting my regular iCloud password *or* my Sandbox password, either.
Post not yet marked as solved
I mention the default Notes app because I'm trying to do something similar. I have a table view of searchable notes. I want everything to be transparent because I have a textured paper background. When you pull the view down, it reveals the search bar.In the stock Notes app, the search bar "has no background and the search bar is translucent", exactly like described in the .minimal style.But when I try to do the same in my app, the search bar has a white background – which stands out against the paper texture. If I view it in the "Debug View Heirarchy" I can see that the search bar does indeed have a white background, even though it's not supposed to.Setting it to .prominent or .default doesn't change anything, like it's completely ignored. I can verify it's still set in updateSearchResults(for:) though.
Post not yet marked as solved
I'm still stuck on this. I have no ideas.
Post not yet marked as solved
This is an app made with Unity, and unfortunately on macOS it doesn't produce an Xcode project (unlike iOS, where it does). I searched through the app bundle and couldn't find any stray Info.plist files – I really couldn't find anything noticeably different from a previous submission that went through.Ultimately, I manually added that line to the Info.plist with a suitable value, and it appears to have been accepted. That feels more like a *workaround* than a *solution*, as I really don't know why it failed in the first place. I don't think that line is *required*.
Post not yet marked as solved
Oof. This sounds like it might be the same issue I'm currently running into.Is this a bug? Is there a workaround that doesn't involve uploading a seed file?
Post not yet marked as solved
I'm still completely stumped on this. I have no idea what to do. Help?
The "guides" I found didn't mention that key, so no. Adding that did fix the issue.However, I have no idea why it would just return nil.
