Skip to content

[in_app_purchase_storekit] Fix Xcode 26.2 analyzer warnings - #10649

Merged
auto-submit[bot] merged 1 commit into
flutter:mainfrom
jmagman:in-app-purchase-analyzer
Dec 19, 2025
Merged

[in_app_purchase_storekit] Fix Xcode 26.2 analyzer warnings#10649
auto-submit[bot] merged 1 commit into
flutter:mainfrom
jmagman:in-app-purchase-analyzer

Conversation

@jmagman

@jmagmanjmagman commented Dec 19, 2025

Copy link
Copy Markdown
Member

Seen in https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8695102947197916049/+/u/Run_package_tests/native_test/stdout

I opened in Xcode 26.2 and let it "Fix".

FIAPPaymentQueueDeleteTests.swift:87:7: warning: 'TARGET_OS_*' preprocessor macros are not available in Swift; use 'os(iOS)' instead
#if TARGET_OS_IOS
^~~~~~~~~~~~~
InAppPurchaseStoreKit2PluginTests.swift:396:25: warning: immutable value 'purchase' was never used; consider replacing with '_' or removing it
case .success(let purchase):
~~~~^~~~~~~~
_
TranslatorTests.swift:18:9: warning: variable 'map' was never mutated; consider changing to 'let' constant
var map: [String: Any] = [
~~~ ^
let

Pre-Review Checklist

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

  1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. 23

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request correctly addresses three analyzer warnings from Xcode 26.2 by updating a preprocessor macro, removing an unused variable, and changing a mutable variable to a constant. The CHANGELOG.md has also been updated. One minor style issue regarding indentation has been pointed out for improvement.

plugin.purchase(id: "consumable", options: nil) { result in
switch result {
case .success(let purchase):
case .success(_):

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The tests are failing - Im guessing you might need to keep the "let purchase" because of IAP sandbox shennanigans. I think if you dont handle the VerificationResult it freaks out. Maybe we can do this instead

case .success(let purchase):
_ = purchase 

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

Weird, this test passes on Xcode 26.2 locally.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

And also passed on 16.4 locally...

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

oh thats scary

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

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

And it passed in CI when run a second time.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ugh the tests are flaky :( thats not good

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@jmagman
jmagmanforce-pushed the in-app-purchase-analyzer branch from c8f9c1b to 150a2aaCompareDecember 19, 2025 18:29
@jmagman
jmagman marked this pull request as ready for review December 19, 2025 19:03
@jmagmanjmagman added the autosubmit Merge PR when tree becomes green via auto submit App label Dec 19, 2025
@auto-submit
auto-submitBot merged commit fb4f0c6 into flutter:mainDec 19, 2025
80 checks passed
@jmagman
jmagman deleted the in-app-purchase-analyzer branch December 19, 2025 20:27
github-merge-queueBot pushed a commit to flutter/flutter that referenced this pull request Dec 23, 2025
flutter/packages@f28cf2e...5e3a766
2025-12-19 49699333+dependabot[bot]@users.noreply.github.com Bump the
all-github-actions group across 1 directory with 2 updates
(flutter/packages#10624)
2025-12-19 magder@google.com [in_app_purchase_storekit] Fix Xcode 26.2
analyzer warnings (flutter/packages#10649)
2025-12-19 49699333+dependabot[bot]@users.noreply.github.com
[dependabot]: Bump the test-dependencies group across 14 directories
with 1 update (flutter/packages#10625)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC flutter-ecosystem@google.com on the revert to ensure that a
human
is aware of the problem.
To file a bug in Flutter:
https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
ivan-vanyusho pushed a commit to ivan-vanyusho/packages that referenced this pull request Jan 26, 2026
…10649)
Seen in https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8695102947197916049/+/u/Run_package_tests/native_test/stdout
I opened in Xcode 26.2 and let it "Fix".
```
FIAPPaymentQueueDeleteTests.swift:87:7: warning: 'TARGET_OS_*' preprocessor macros are not available in Swift; use 'os(iOS)' instead
#if TARGET_OS_IOS
^~~~~~~~~~~~~
```
```
InAppPurchaseStoreKit2PluginTests.swift:396:25: warning: immutable value 'purchase' was never used; consider replacing with '_' or removing it
case .success(let purchase):
~~~~^~~~~~~~
_
```
```
TranslatorTests.swift:18:9: warning: variable 'map' was never mutated; consider changing to 'let' constant
var map: [String: Any] = [
~~~ ^
let
```
## Pre-Review Checklist
**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
creatorpiyush pushed a commit to creatorpiyush/packages that referenced this pull request Jun 10, 2026
…10649)
Seen in https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8695102947197916049/+/u/Run_package_tests/native_test/stdout
I opened in Xcode 26.2 and let it "Fix".
```
FIAPPaymentQueueDeleteTests.swift:87:7: warning: 'TARGET_OS_*' preprocessor macros are not available in Swift; use 'os(iOS)' instead
#if TARGET_OS_IOS
^~~~~~~~~~~~~
```
```
InAppPurchaseStoreKit2PluginTests.swift:396:25: warning: immutable value 'purchase' was never used; consider replacing with '_' or removing it
case .success(let purchase):
~~~~^~~~~~~~
_
```
```
TranslatorTests.swift:18:9: warning: variable 'map' was never mutated; consider changing to 'let' constant
var map: [String: Any] = [
~~~ ^
let
```
## Pre-Review Checklist
**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmitMerge PR when tree becomes green via auto submit Appp: in_app_purchaseplatform-iosplatform-macos

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@jmagman@LouiseHsu