Locale.current.currency?.identifier: Skip is unable to determine the owning type...

[djryanash]

Here:

public var body: some View {
        Form {
            Section {
                TextField("Amount", value: $checkAmount, format: .currency(code: Locale.current.currency?.identifier ?? "USD"))
            }
            Section {
                Text(checkAmount, format: .currency(code: Locale.current.currency?.identifier ?? "USD"))
            }
        }
    }

I'm getting:

Skip is unable to determine the owning type for member 'currency'. This often occurs when other issues prevent Skip from matching the surrounding API call, and it may resolve when those issues are fixed. Or add the owning type explicitly (e.g. MyType.currency)

EDIT: I see that the Locale API is fully supported via SkipFoundation.

[aabewhite]

Sorry for the trouble. It turns out that neither Text/TextField(_:, value:, format:) nor Locale.currency are supported yet. The fact that we have Locale listed as fully supported is an error. When we imported the APIs from Foundation we didn't get all the extensions, so sometimes we think we've covered the entire API when we haven't. We'll make sure to update the doc.

We do support Locale.currencySymbol, although I know that's not exactly what you want. Of course you can still use whatever you want on iOS, but you'd have to do the formatting yourself on Android. Something to the effect of:

#if !SKIP
Text(checkAmount, format: .currency(...))
#else
... Android solution ...
#endif

We'll consider this a feature request for these APIs!

[djryanash]

Is "Skip is unable to determine the owning type..." a typical error for yet-to-be-supported Swift code? Are there any other errors I should be on the lookout for to determine if code has been implemented or not?

[marcprux]

Is "Skip is unable to determine the owning type..." a typical error for yet-to-be-supported Swift code? Are there any other errors I should be on the lookout for to determine if code has been implemented or not?

Generally speaking, we try to mark missing API as unavailable in SKIP, which will raise a clearer error:

This API is not yet available in Skip.
Consider placing it within a #if !SKIP block.

We have fairly good coverage of this in SkipUI, but SkipFoundation is still missing a number of them. In these cases, you'll either see the "Skip is unable to determine the owning type..." error, or else simply a "Missing type" error from the Kotlin compiler.