-
Notifications
You must be signed in to change notification settings - Fork 441
Some automations for Android #198
Changes from all commits
2bef6aa
0232c38
a3e2922
ea37088
b9e1339
ee213d7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -38,3 +38,5 @@ dependencies { | |
// compile "com.google.android.gms:play-services-auth:9.6.+" | ||
|
||
} | ||
|
||
apply plugin: "com.google.gms.google-services" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sadly on my machine this leads to:
I'm running tns 2.3.0.. perhaps this changed in a more recent version? Still applying the plugin at the bottom of There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The 'com.google.gms.google-services' plugin still has to be added by hand in the The 'com.google.gms.google-services' can be somewhat automated using an additional after prepare hook like the one here:
But it looks far to fragile for me to push this in the firebase plugin. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you double check if it works when you add by hand this in platform/android:
Without the:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Indeed, adding I see what you mean with the after prepare hook but I think it's worth the brittleness to include it in the plugin. Worst case scenario the developer still needs to add the classpath by hand but generally this would make installation lots easier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! Do you think we'd be able to add this to the postinstall script? Not as part of this PR, just would like to know if you think it would be a wise thing to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is ok for the plugins to require some modifications to be done by hand, as long as these modifications can be kept in source control and are well documented.
If the changes happen to be in platforms/* then it would be best if there is an automated way to apply them (using hooks?) so the app can roundtrip source control and continuous integration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍