Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge changes from beta 20.9.0.1 into trunk #19438

Merged
merged 10 commits into from
Oct 12, 2022
Merged

Merge changes from beta 20.9.0.1 into trunk #19438

merged 10 commits into from
Oct 12, 2022

Conversation

mokagio
Copy link
Contributor

@mokagio mokagio commented Oct 12, 2022

  • Updates to the localization files (.strings and Fastlane metadata) automatically pulled for the new translations that have already been approved in GlotPress
  • Version update in .xcconfig
  • Diffs from the PRs that made it into this beta

Includes:

staskus and others added 10 commits October 7, 2022 18:12
…pping-account-settings-menu-for-accounts-with-no-sites

Fix crash on tapping Account Settings menu for accounts with no sites
Without any apparent change on our side, we saw a couple of Pocket Casts
builds with unexpected, and unexpectedly incrementing, build numbers on
TestFlight. From 7.24.0.3, to 8, to 9.

This behavior could be replicated locally in that project by running the
Fastlane automation, but not when archiving via Xcode.

I pin pointed it to the `manageAppVersionAndBuildNumber` option being
true by default in the `ExportOptions.plist` that Fastlane /
`xcodebuild` generates for `gym` to convert an archive into an IPA.

Explicitly setting the option to `false` solves the issue locally.

See Automattic/pocket-casts-ios#373.

To verify the issue on this project, checkout the current tip of the
release branch, 838058f, and apply the
following patch:

```
index 1c05a77b05..e3cb20e4ae 100644
--- a/fastlane/lanes/build.rb
+++ b/fastlane/lanes/build.rb
@@ -123,6 +123,8 @@ platform :ios do
       export_options: { method: 'app-store' }
     )

+    UI.user_error! 'Aborting after building. This was just a test.'
+
     testflight(
       skip_waiting_for_build_processing: true,
       team_id: get_required_env('FASTLANE_ITC_TEAM_ID'),
@@ -173,6 +175,8 @@ platform :ios do
       export_options: { method: 'app-store' }
     )

+    UI.user_error! 'Aborting after building. This was just a test.'
+
     testflight(
       skip_waiting_for_build_processing: true,
       team_id: '299112',
@@ -215,6 +219,8 @@ platform :ios do
       export_options: { method: 'enterprise' }
     )

+    UI.user_error! 'Aborting after building. This was just a test.'
+
     appcenter_upload(
       api_token: get_required_env('APPCENTER_API_TOKEN'),
       owner_name: APPCENTER_OWNER_NAME,
@@ -264,6 +270,8 @@ platform :ios do
       export_options: { method: 'enterprise' }
     )

+    UI.user_error! 'Aborting after building. This was just a test.'
+
     appcenter_upload(
       api_token: get_required_env('APPCENTER_API_TOKEN'),
       owner_name: APPCENTER_OWNER_NAME,
@@ -317,6 +325,8 @@ platform :ios do
       export_options: { method: 'enterprise' }
     )

+    UI.user_error! 'Aborting after building. This was just a test.'
+
     appcenter_upload(
       api_token: get_required_env('APPCENTER_API_TOKEN'),
       owner_name: APPCENTER_OWNER_NAME,
```

Run a lane to build a binary for App Store Connect
(`method: 'app-store'`) and notice how the build number is `21` instead
of the `20.9.0.0` coming from `config/Version.public.xcconfig`.

```
bundle exec fastlane build_and_upload_app_store_connect skip_confirm:true skip_prechecks:true
```

Conversely, a lane with `method: 'enterprise'` won't show that behavior:

```
bundle exec fastlane build_and_upload_app_center skip_confirm:true skip_prechecks:true
```
… is showing (#19417)

* Explicitly set insights as selected period when grow audience is showing

When we simply return, we can get into cases where selectedPeriod is not equal to .insights even though insights are open. In such an instance the tab switching doesn't work anymore.

* Update expected Bundler to version 2.3.23

Co-authored-by: Gio Lodi <[email protected]>
@wpmobilebot
Copy link
Contributor

You can test the changes in Jetpack from this Pull Request by:
  • Clicking here or scanning the QR code below to access App Center
  • Then installing the build number pr19438-446cd4b on your iPhone

If you need access to App Center, please ask a maintainer to add you.

@wpmobilebot
Copy link
Contributor

You can test the changes in WordPress from this Pull Request by:
  • Clicking here or scanning the QR code below to access App Center
  • Then installing the build number pr19438-446cd4b on your iPhone

If you need access to App Center, please ask a maintainer to add you.

Copy link
Contributor

@AliSoftware AliSoftware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit: 👍


PS: 🤦 Facepalm moment from me while reviewing this…

Includes:

#19417 by @staskus
#19418 by @staskus

At first I thought that, while I saw #19418 in the list of commits, I didn't see #19417 so I thought it wasn't part of this PR unlike what was said in the PR description. I then thought maybe it was merged into trunk as part of a previous release/20.9->trunk PR hence why it wasn't there, but couldn't find it in any of those previous PRs…

It took me a minute to realize that #19417 was indeed part of this PR and in the commit list after all (unlike what I thought at first)… it's only that the reference to that PR number was hidden at first due to a long commit message being collapsed 😅 Once I saw in the 19417 PR which commit was associated with that PR being merged (namely, ac66570), and then found that commit in this PR's commit list and expanded the commit message details, it suddenly all made sense 😅
image

@mokagio mokagio merged commit 65f1ad6 into trunk Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants