Skip to content

Merge release/26.1 into trunk#22138

Merged
oguzkocer merged 7 commits intotrunkfrom
merge/release-26.1-into-trunk
Aug 15, 2025
Merged

Merge release/26.1 into trunk#22138
oguzkocer merged 7 commits intotrunkfrom
merge/release-26.1-into-trunk

Conversation

@wpmobilebot
Copy link
Contributor

Merging release/26.1 into trunk.

Via intermediate branch merge/release-26.1-into-trunk, to help fix conflicts if any:

                            release/26.1  ----o-- - - -
                                               \
           merge/release-26.1-into-trunk        `---.
                                                     \
                                   trunk  ------------x- - -

@wpmobilebot wpmobilebot added the Releases Label related to managing releases label Aug 15, 2025
@wpmobilebot wpmobilebot added this to the 26.2 milestone Aug 15, 2025
@dangermattic
Copy link
Collaborator

1 Message
📖 This PR has the Releases label: some checks will be skipped.

Generated by 🚫 Danger

oguzkocer and others added 7 commits August 15, 2025 15:55
* Remove isEditorStarted flag to fix content loss during activity restart

The isEditorStarted flag was preventing editor reinitialization during
activity restarts, but this caused content loss because:

1. Activity restart triggers new fragment creation
2. isEditorStarted gets reset to false in onDestroy()
3. startWithEditorSettings() gets called but always rebuilds from original data
4. Current editor content is lost instead of being preserved

Root cause: The flag was designed to prevent duplicate initialization within
a single fragment instance, but during activity restarts, we WANT the editor
to reinitialize with the current content, not block reinitialization entirely.

Changes:
- Remove isEditorStarted field and related state management
- Remove isEditorStarted checks in startWithEditorSettings()
- Allow editor to reinitialize after activity restart
- Fixes content loss during dark mode toggle

* Fix double ViewPager setup during auth state changes

Prevent duplicate editor initialization by:
1. Only calling fetchWpComCookies() if not already in Success state
2. Adding ViewPager state check to prevent duplicate setup
3. Using distinctUntilChanged() to prevent duplicate LiveData emissions
4. Consolidating Success handling logic in handleSuccessfulAuth()

Changes:
- Check auth state before calling fetchWpComCookies()
- Add ViewPager adapter check with error logging for duplicate setup attempts
- Add distinctUntilChanged() to auth state observer
- Extract handleSuccessfulAuth() for consistent Success state handling
- Remove debug logging from production code
@oguzkocer oguzkocer force-pushed the merge/release-26.1-into-trunk branch from 3feada7 to b4e577b Compare August 15, 2025 19:55
@oguzkocer oguzkocer enabled auto-merge (squash) August 15, 2025 19:57
@wpmobilebot
Copy link
Contributor Author

Project manifest changes for WordPress

The following changes in the WordPress's merged AndroidManifest.xml file were detected (build variant: wordpressVanillaRelease):

--- ./build/reports/diff_manifest/WordPress/wordpressVanillaRelease/base_manifest.txt	2025-08-15 20:00:32.605630562 +0000
+++ ./build/reports/diff_manifest/WordPress/wordpressVanillaRelease/head_manifest.txt	2025-08-15 20:00:40.095658973 +0000
@@ -2,8 +2,8 @@
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
     package="org.wordpress.android"
     android:installLocation="auto"
-    android:versionCode="1471"
-    android:versionName="26.1-rc-1" >
+    android:versionCode="1472"
+    android:versionName="26.1" >
 
     <uses-sdk
         android:minSdkVersion="26"

Go to https://buildkite.com/automattic/wordpress-android/builds/23085/canvas?sid=0198af4d-c857-4985-9433-396706c8733e, click on the Artifacts tab and audit the files.

@wpmobilebot
Copy link
Contributor Author

Project manifest changes for WordPress

The following changes in the WordPress's merged AndroidManifest.xml file were detected (build variant: jetpackVanillaRelease):

--- ./build/reports/diff_manifest/WordPress/jetpackVanillaRelease/base_manifest.txt	2025-08-15 20:00:48.326173837 +0000
+++ ./build/reports/diff_manifest/WordPress/jetpackVanillaRelease/head_manifest.txt	2025-08-15 20:00:55.956250763 +0000
@@ -2,8 +2,8 @@
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
     package="com.jetpack.android"
     android:installLocation="auto"
-    android:versionCode="1471"
-    android:versionName="26.1-rc-1" >
+    android:versionCode="1472"
+    android:versionName="26.1" >
 
     <uses-sdk
         android:minSdkVersion="26"

Go to https://buildkite.com/automattic/wordpress-android/builds/23085/canvas?sid=0198af4d-c858-423d-bbed-9077de10a9d3, click on the Artifacts tab and audit the files.

@sonarqubecloud
Copy link

@wpmobilebot
Copy link
Contributor Author

Jetpack📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
App NameJetpack Jetpack
FlavorJalapeno
Build TypeDebug
Versionpr22138-b4e577b
Commitb4e577b
Direct Downloadjetpack-prototype-build-pr22138-b4e577b.apk
Note: Google Login is not supported on these builds.

@wpmobilebot
Copy link
Contributor Author

WordPress📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
App NameWordPress WordPress
FlavorJalapeno
Build TypeDebug
Versionpr22138-b4e577b
Commitb4e577b
Direct Downloadwordpress-prototype-build-pr22138-b4e577b.apk
Note: Google Login is not supported on these builds.

@oguzkocer oguzkocer merged commit 119e6c3 into trunk Aug 15, 2025
25 of 28 checks passed
@oguzkocer oguzkocer deleted the merge/release-26.1-into-trunk branch August 15, 2025 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Releases Label related to managing releases

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants