react-native-acoustic-connect-beta 19.0.33 → 19.0.35

package/CHANGELOG.md

@@ -1,3 +1,13 @@
+## 19.0.35 (2026-09-23)
+
+### Reverts
+
+* Revert "Beta ReactNativeConnect build: 18.0.36" ([609ad7d](https://github.com/aipoweredmarketer/react-native-acoustic-connect-beta/commit/609ad7d3244ec06f27dced5864d40585c5b3c9cf))
+## 19.0.34 (2026-09-22)
+
+### Reverts
+
+* Revert "Beta ReactNativeConnect build: 18.0.36" ([609ad7d](https://github.com/aipoweredmarketer/react-native-acoustic-connect-beta/commit/609ad7d3244ec06f27dced5864d40585c5b3c9cf))
 ## 19.0.33 (2026-09-22)
 
 ### Reverts

package/README.md

@@ -106,6 +106,29 @@ directories, and re-running either command is safe. After install, run
 `npx acoustic-connect doctor` to validate the result — see
 [Setup CLI](#setup-cli-acoustic-connect) below.
 
+### Where the Android Connect SDK is resolved from
+
+You don't need to add any repositories. This package's `android/build.gradle`
+declares both of the ones it needs, and your app inherits them:
+
+| Repository | Carries |
+| --- | --- |
+| [`go-acoustic/Android_Maven`](https://github.com/go-acoustic/Android_Maven) | Beta builds (`-beta` versions) |
+| Maven Central | Release builds and the older version history |
+
+Beta artifacts are published only to the GitHub-hosted repository, so a build
+that does not declare it never sees them. When `AndroidVersion` is empty the
+version is resolved dynamically, and Gradle takes the newest match across
+*both* repositories — the beta repository does not need to be consulted first
+for a new beta to win. It is scoped to the `io.github.go-acoustic` group, so
+nothing else in your build is routed through it, and Maven Central still
+answers for any version the beta repository does not carry.
+
+This matters when you pin. Leaving `AndroidVersion` empty resolves the newest
+version in the supported range across **both** repositories — which, for as
+long as betas are the newest builds, means a `-beta`. Pin `AndroidVersion` to
+a specific release if you would rather track Maven Central's release line.
+
 ## Setup CLI (`acoustic-connect`)
 
 The package ships a small CLI, installed as `acoustic-connect` (invoke it with
@@ -957,6 +980,13 @@ leave it empty for the newest 11.x available). 12.x is intentionally outside
 the supported range pending compatibility validation — track that work
 separately if you need it.
 
+If the version you pinned is a `-beta`, check that your build can reach
+[`go-acoustic/Android_Maven`](https://github.com/go-acoustic/Android_Maven) —
+beta artifacts live there rather than on Maven Central. This package declares
+that repository for you, so a failure here usually means the build is offline
+or behind a proxy that blocks `raw.githubusercontent.com`. See
+[Where the Android Connect SDK is resolved from](#where-the-android-connect-sdk-is-resolved-from).
+
 ### Gradle can't find `node`
 
 Common when Gradle is launched outside an NVM-loaded shell. Either:

package/android/build.gradle

@@ -173,6 +173,39 @@ repositories {
 allprojects {
     repositories {
         google()
+
+        // Beta Connect artifacts publish HERE, not to Maven Central. Central is
+        // still consulted below — it carries every version up to 11.0.31-beta —
+        // but newer betas land only in this GitHub-hosted Maven tree, so a build
+        // that does not know about it silently freezes `connect:+` at whatever
+        // Central happens to hold. That failure is invisible: resolution
+        // succeeds, just against a stale SDK, and the gap widens with each beta.
+        //
+        // Declaring it is what fixes that; the position is close to cosmetic.
+        // `connect` is resolved through a dynamic version, and for those Gradle
+        // queries every declared repository and takes the newest match across
+        // all of them rather than stopping at the first repository that answers.
+        // Verified: with this entry declared LAST, after mavenCentral(),
+        // `connect:+` still resolves to the newest beta here rather than to
+        // Central's older newest. Order only decides which repository serves a
+        // PINNED version that both carry, where the artifact is identical
+        // anyway — it is kept first so a pin on a beta is served by the tree
+        // that is authoritative for betas.
+        //
+        // The content filter is not cosmetic. Without it every dependency in
+        // the build (React Native, Kotlin, AndroidX, …) would hit
+        // raw.githubusercontent and 404 before falling through to a repository
+        // that has it. Inclusive `content`, not `exclusiveContent`, so Central
+        // still answers for versions this tree does not carry.
+        //
+        // Declared only here, not also in the top-level `repositories` block:
+        // `allprojects` covers this project too, so both would feed the same
+        // resolution and the pair could drift.
+        maven {
+            url = "https://raw.githubusercontent.com/go-acoustic/Android_Maven/master"
+            content { includeGroup "io.github.go-acoustic" }
+        }
+
         mavenCentral()
         maven { url="https://s01.oss.sonatype.org/content/groups/staging" }
 

package/android/src/main/assets/ConnectBasicConfig.properties

@@ -1,4 +1,4 @@
-#Tue Sep 22 10:59:14 GMT 2026
+#Wed Sep 23 12:48:37 GMT 2026
 UseWhiteList=true
 PrintScreen=3
 UseRandomSample=false

package/package.json

@@ -227,7 +227,7 @@
     "source": "src/index",
     "summary": "react-native ios android tealeaf connect cxa wxca er enhanced-replay",
     "types": "./lib/typescript/src/index.d.ts",
-    "version": "19.0.33",
+    "version": "19.0.35",
     "workspaces": [
         "example",
         "Examples/bare-workflow"