Ok, silly mistake by me. Please try b3ce15a30f88531b060534217b109c309f84e066
instead.
Iāve updated the download links in the top post.
Awesome! It doesnāt crash now, but the coordinates are not correct either: https://github.com/defold/editor2-issues/issues/2893
Great!
Iād like to use Admob and Firebase together.
Can I help with some tests in my project, or do I just have to wait for new extensions?
Firebase Analytics already has a gradle file:
(Note that you do not need to add the base extensions anymore. The read me file will be updated to reflect this once 1.2.165 is released)
We need @sergey.lerg to update his extension with a gradle file as well (or if you fork it, test it and submit a pull request yourself).
I am getting an error when trying to build for iOS.
Directory 'build/default/manifests' could not be created
Creating the directory manually doesnāt help. What to do?
Iāve updated the download links with the newest version: 4f15d336c3ef1b3123fd1ceaae04813d2b7ae86e
Yup. Can confirm it works great now.
Iāve updated the download links with the latest version, which fixes this bundling issue: a404b463128a6eecf3d5cce4916180b222488123
Iāve tried to modify @sergey.lergās admob-extension, but it is not clear to me what dependencies to add in build.gradle to make it work properly
The dependencies should be listed in the official AdMob documentation:
The example on that page shows this:
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'androidx.appcompat:appcompat:1.0.2'
implementation 'com.google.android.gms:play-services-ads:18.3.0'
}
And I believe that what you need is only the com.google.android.gms:play-services-ads
dependency in the build.gradle file for the AdMob extension. Ignore the other two lines.
dependencies {
implementation 'com.google.android.gms:play-services-ads:18.3.0'
}
Version 18.3.0 does however use AndroidX and that could cause a conflict with other extensions (maybe). In that case you can try an older version of com.google.android.gms:play-services-ads
. Available versions can be seen here for instance:
https://mvnrepository.com/artifact/com.google.android.gms/play-services-ads
My apologize for the following maybe stupid question. I am using 1.2.164 and the editor show me āUpdate Availableā. Is this 1.2.165 or just the Beta? I have never downloaded a Beta and I would prefer not.
Thanks!
In your āAboutā dialog, you should see channel: editor-alpha
which is the up-to-date editor changes, together with the latest engine release (1.2.164).
Clicking the Update
button will give you the next release in that channel.
You can check the about dialog afterwards to confirm.
I am sorry, but probably I am missing something. With āUpdate Buttonā do you mean the text āUpdate Availableā in the right bottom corner of the editor?
(Just to confirm: I read āeditor-alphaā and ā1.2.164ā as engine release)
On Windows this setting is shared by all version of Defold Editor
Iāve changed it in 1.2.165 beta, but it appears also in 1.2.164
Yeah, but it seems that even with build-stage
, building with NEs on 1.2.164 will work correctly, so unless it causes issues, Iāll leave it like that.
@mats.gisselson pushed an editor fix yesterday and that fix should go straight to production. This is probably why you have an update.
40e9ca1299d22eed12bb0148ed117f418162cb19
Released a new beta right now with a fix for this issue where the android resources in the project.bundle_resources
werenāt used.
Also, even failed builds now output a log.txt
file from the extender server, in the <project folder>/build/<platform>/log.txt
The planned release of 1.2.165 has run into an Apple Notarization issue (https://developer.apple.com/news/?id=12232019a). We are working to resolve the problem and hope to release tomorrow instead.