You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
adb shell am start -n dev.hyo.martie/.MainActivity
47
+
```
48
+
49
+
With flavors enabled, Gradle no longer creates the generic `installDebug`/`assembleDebug` tasks—run the flavor-specific tasks explicitly in scripts, CI pipelines, and IDE run configurations.
50
+
36
51
## Generated Types
37
52
38
53
- All GraphQL models in `openiap/src/main/java/dev/hyo/openiap/Types.kt` are generated from the [`hyodotdev/openiap-gql`](https://github.com/hyodotdev/openiap-gql) repository. When you update API behavior, adjust the upstream type generator first so the Kotlin output stays in sync across platforms.
Set the target billing provider via `BuildConfig` fields (default is `play`). The library will also auto-detect Horizon hardware when `auto` is supplied.
59
+
60
+
```kotlin
61
+
android {
62
+
defaultConfig {
63
+
buildConfigField("String", "OPENIAP_STORE", "\"auto\"") // play | horizon | auto
adb shell am start -n dev.hyo.martie/.MainActivity
186
+
```
187
+
188
+
For standard Google Play workflows, run the matching `play` tasks (`:openiap:assemblePlayDebug`, `:Example:installPlayDebug`). Flavors remove the generic `installDebug` task, so always target the desired flavor explicitly when using the CLI, CI, or IDE run configurations.
0 commit comments