What navigation bar instance are you modifying? Normally you get a reference to the nav bar from your UINavigationController, not from your own stored property or outlet or whatever _myNavBar and self.navbar are in your example.

I’m not sure about views, but constraints do have an “identifier” property that you can set in code or IB (using the attributes inspector) to make analyzing the logs easier. Lots of tips on debugging auto layout here: https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/AutolayoutPG/TypesofErrors.html#//apple_ref/doc/uid/TP40010853-CH17-SW1

Is it possible this is the so-called “StoreKit flow” where the user is directed to the App Store app to update an expired credit card for example? In that situation, your transaction observer will receive two callbacks - the first failed, and the second success. Your code needs to be able to handle that case. Unfortunately I’m not aware of any way to simulate it to test said code. 😕

Are you setting the numberStyle property of the formatter to one of the currency styles? Are you using localizesFormat to prevent the formatter from using the default separators and currency symbol from the locale?

@Yagizzhan: SwiftUI is the future but it’s still half baked. That may change in a day or two 🙂 Even so, I’d recommend SwiftUI since it’s not too difficult to use UIKit views in places where SwiftUI has no support yet.

That question is a bit too broad to give any answer. You will have to break it up into manageable pieces. For example how to build your overlays/annotations to look the way you want how to perform your database query when to perform the DB query - e.g. in response to the map view regionDidChangeAnimated If you’re making a network request to the DB, i.e. it’s not embedded in your app bundle, then you’ll have to debounce / rate limit your queries and deal with error conditions and query results coming in asynchronously. If you have specific questions that come up it would be better to post those individually rather than a general “how do I write an app to do this” question.

You need to open that crash log in Xcode so it gets symbolicated. Then the section “Last Exception Backtrace” will contain the stack trace that caused the problem. Without being symbolicated, it’s not possible to determine anything.

Maybe off topic, but I thought it was not allowed to call verifyReceipt directly from the app. Is this a supported configuration? I suppose you’d have the same issue trying to find the receipt to upload to your server.

A common cause of this is forgetting to set the dataSource and delegate properties on the table view.

Your app will run, if it’s distributed ad hoc, via TestFlight or the App Store. But the old Xcode version will not be able to run development builds directly on the new OS. You’ll need Xcode 12 for that. Whether it will run without crashing is anybody’s guess 🙂 That’s why they give us early beta access, to fix any unexpected issues. Also keep in mind that there’s a requirement coming Real Soon Now (can’t remember the exact date, but it’s soon) that all updates must be built using the iOS 13 SDK, i.e. Xcode 11. So you’ll need to update to that version at least.

You would add sufficient constraints on the storyboard to keep IB happy, but mark them as “Placeholder (remove at build time)”. There’s a checkbox over in the Attributes inspector for the constraint.

The platform check syntax for Swift is #if os(macOS) ... #elseif os(iOS) ... #endif That gives coarse grained control. If you need to check availability of specific APIs or specific OS versions you’ll need to use @available.

Apple provides a little bit of data on the App Store developer page: https://developer.apple.com/support/app-store/ Personally for a new app releasing in 6+ months I’d probably go iOS 14. You could say iOS 13 but all those devices can upgrade to 14, so adoption will probably be very high. You could argue that people who aren’t willing to update their devices after all those years aren’t as likely to spend money on new apps anyway.

Had a reply all typed out, switched tabs, switched back and it’s all gone. !@$* new forums. You should be able to fix it by marking that action parameter as @escaping. It has to be marked as such because the parameter goes out of scope before the closure is executed.

Unfortunately the title is not self explanatory. What warnings are you talking about? What do “context menus” have to do with it? Can you post the actual error messages (copied and pasted, not just your interpretation) and some simple code that demonstrates the problem? Without any details of the specific layout and the specific error messages you’re getting, all anyone can do is point you towards the Auto Layout Programming Guide - https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/AutolayoutPG/index.html.