-
New to Skip so still getting my sea legs, so to speak. I'm finding a few things missing in the skip-firebase package and was curious the best path forward. For example, the app i'm working to port uses PhoneAuthProvider from the iOS sdk which isn't yet in there. Are folks forking skip-firebase and adding what they need? Or is there some other better approach? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 14 replies
-
Much of our Firebase functionality has been added through pull requests. The recommended approach is to fork the repository and add your fork's local clone to an Xcode workspace alongside your app project so that it can be developed in tandem with your app, and then when you have the functionality you need ready to go, file a new PR from your fork. We describe the process at https://skip.tools/docs/contributing/#local-libraries. Let us know if there is anything we can help with! |
Beta Was this translation helpful? Give feedback.
-
@marcprux Thank you. The biggest issue is there is no code or examples that illustrates how numeric types come back from Firestore. Even the example FireSide project, the Message type only shows strings and dates. This should be straight forward but goodness i cannot for the life of me figure out how to convert an Any that is coming back from a Number field in firestore to a usable Double on the swift side. DocumentSnapshot.get(fieldName) works great for String. Works great for Date (via firestore's dumb Timestamp type). But any number time works on the iOS side but not on the transpiled kotlin side. Suggestions on best way to debug? |
Beta Was this translation helpful? Give feedback.
-
@marcprux I have additional info... I have found a workaround but i suspect there is some lower level issue... Its an issue with this method in SkipFirebaseFirestore...
The ifs all work fine, but the final else. If the resulting value:Any is a
Should that be necessary? Thank you! |
Beta Was this translation helpful? Give feedback.
Much of our Firebase functionality has been added through pull requests. The recommended approach is to fork the repository and add your fork's local clone to an Xcode workspace alongside your app project so that it can be developed in tandem with your app, and then when you have the functionality you need ready to go, file a new PR from your fork. We describe the process at https://skip.tools/docs/contributing/#local-libraries.
Let us know if there is anything we can help with!