Solar2D 2025.3721 has been released

Solar2D Daily Builds and Public Releases
#22

Understood. I suppose it would have been done already if it was simple, but thought it was worth double checking.

#23

Hey @bgmadclown, this platform option was added to Solar2D some time ago, but it’s not mentioned in the documentation: "android-nongoogle" in build.settings, which controls plugin availability.

Here’s an example of how I used it:

["plugin.google.iap.billing.v2"] = {
    publisherId = "com.solar2d",
    supportedPlatforms = { android = true, ["android-nongoogle"] = false }
}

When you see "android-nongoogle", you might think it refers to all Android stores except Google Play. I tested it by setting Target App Store to "none", expecting the plugin to be excluded, but it still ended up in the APK.

In this post Kan98 suggests it may only apply to the Samsung Store. I tried setting Target App Store to "Samsung" as well, but the plugin still got included.

So, it’d be helpful to clarify how "android-nongoogle" actually works, and I think it definitely deserves a mention in the official docs.

#24

image
image809×200 5.5 KB

Yeah, it will be set when target store is samsung.

1 Like
#25

Can we add the platform for the key as Samsung or would it be better as Samsung Galaxy Store?:

I can put it as @Kan98 describes it, “You need to set build target to Samsung for the key to activate.” Is that the correct way to describe it?

#26

I think just add into table
image
[“android-nongoogle”] = Samsung

image

#27

Done.

1 Like
#28

Great job !

1 Like
#29

All of this is quite confusing, and I believe that associating “android-nongoogle” with builds targeting Samsung makes things even more complicated.

Let’s analyze the situation: there are currently specific parameters for Amazon and the App Store. Also, using just “android” is commonly understood to mean a build intended for Google Play. In that context, the most logical and helpful approach for developers would be to use “android-nongoogle” for builds that are not targeting any of the major app stores like Google Play or the Galaxy Store.

In addition, I suggest introducing a new parameter, such as “galaxy”, specifically for builds targeting the Samsung Galaxy Store (whent you set Target App Store as Samsung), with plugin availability adjusted accordingly.

In my case, I distribute my games through several channels, including one with a Russian company. To generate builds for them, I have to create a separate build.settings file, removing all permissions required by Google Play and any Play Store–specific plugins. Since I can’t have both versions of the build.settings file in the same project, I currently switch them manually—backing up the original and replacing it with the custom one each time I need to build for that company.

If the suggestions above were implemented, the whole process would be much cleaner, more organized, and more practical for developers working with multiple distribution channels.