You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.
Just to note, I have the same apparent conflict with StoreKit, but the normal fix of just using the module to specify which one I want (e.g., InAppPurchase.Product) also fails with: 'Product' is not a member type of class 'InAppPurchase.InAppPurchase', which makes it seem like something in the way this framework is designed has put me in a corner. (Actually, I'm really not sure why the compiler thinks it's a class...?? I don't see any weird singleton design... strange...)
Okay, no, I get it. The main class in InAppPurchase is called InAppPurchase, so you can't actually use the module to narrow the scope... bummer. Only solution was to make sure StoreKit and InAppPurchase don't appear in the same file.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
I get an error about
'Product' is ambiguous for type lookup in this context
To Reproduce
Steps to reproduce the behavior:
Any mention of
Product
Expected behavior
Not throw an error, maybe it needs to be renamed?
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: