Thanks, I updated the steps. I think a pre release version of the plugin was called AdvancedNoise, but it was quite a while ago.
Glad you like it! Was just a bit of fun on my part, but became my standard theme.
I think I did look at doing a dark mode version, but in the style of the default theme. It was too much work unfortunately. But I'd be happy someone using this as a basis for their own dark mode theme.
Refactoring may not be glamorous but it's an important part of development.
This article codecademy.com/articles/tdd-red-green-refactor talks about the 3 stages of test driven development, but in practice even if you aren't using tests it helps to follow these 3 steps:
1. Consider what it should do.
2. Build something that matches that.
3. Consider how to improve it.
It's not uncommon to follow only the first 2 steps, but without step 3 those first 2 steps will get progressively more difficult!
So try not to feel bad about not adding anything new, refactoring is equally important!
While it would be nice to support such an option it's worth noting that Apple only provide 2 options to upload an app archive to the store. Both require having a Mac, and the easiest solution uses xcode. So any gain from being able to build an archive via the build service would be counteracted by that unfortunately.
Color quantization reduces the number of colours in an image to 256 so that it can use the PNG palette mode. This is a form of lossy compression. Depending on the image you might get visible artifacts.
Have you looked at: construct.net/en/forum/construct-3/how-do-i-8/breaking-change-mobile-advert-145087 ?
If your configuration is correct, but the app is still crashing file a bug report at github.com/Scirra/Construct-3-bugs
On Android the dialog will always show, because it's a generic dialog not one specific to rating an app. On iOS you can show it up to 3 times per year. Check out our documentation construct.net/en/make-games/manuals/construct-3/plugin-reference/share and Apples guide on when you should request ratings developer.apple.com/design/human-interface-guidelines/ios/system-capabilities/ratings-and-reviews
It's also worth noting that debug versions on iOS always show the dialog, and testflight never show it.
I believe C3 renames the main .exe file of your export, but C2 doesn't. Otherwise the process is exactly the same, as it's using a 3rd party tool to modify an exported game.
Apple is quite restrictive on this, the API is basically fire and forget. It doesn't tell you if the dialog opened or if they rated the app. I haven't been to look at the related guidelines but I'm guessing they don't like giving prizes to users based on this.
If your not using the "rate app" actions in the Share plugin then remove the "construct-mobile-rate" cordova plugin from your config.xml file. It's not currently compatible with PhoneGap Build due to it using swift.
A few notes for those of you experimenting with rating applications.
Apple has some great tips for WHEN to request app ratings.
When using the "Request app rating" on iOS live apps will only show the alert to a user 3 times in a year, so be frugal! The parameters for this action are only required for Android.
The "Display store page" takes your application package name on Android ( e.g. com.company.example ) and your store ID on iOS ( if you have link like "https://itunes.apple.com/app/id375380948" it's the number after "id" ). This action isn't limited to the current app, but be careful about store rules when showing links to other apps.
The C3 runtime uses webassembly for some features, but the simulator doesn't support it. Apple hasn't commented on the fact, but they must be aware of it. In my testing app rating works on a physical device provided your debugging from xcode.
The SHA-1 signature is for the keystore, not the APK. So you can start the export process to get a keystore and it's signature then cancel the export. You can use that keystore for as many builds and apps as you like.
Strelya72 Release notes is not the place to file bug reports, please use our issue tracker github.com/Scirra/Construct-3-bugs/issues.
We already target SDK 28, and have done for quite awhile. You can see the target in your log message, which unfortunately does not include any actual errors. If your project is not exporting for some reason then please file a bug for us including the affected project and your export settings.
It should not have affected the behaviour of existing projects. We have had one reported issue related to timelines/tweens (they leverage the same core code) in the new release which might be the same issue as yours github.com/Scirra/Construct-3-bugs/issues/3296
Member since 8 Mar, 2016
The official blog for all things Construct and Scirra run by our employees!