NixOS Widevine Not Recognized

Platform: NixOS 23.0.1 (development)
Version: ECSv26.6.0 (also tested with 27.1.0)
Hello,
I'm building an application in Electron meant to interact with content that requires Widevine's CDM. I'm aware that Linux is a funky child when it comes to CDM, and that ECS is not immune to this, although I am not sure that this is even the issue.
Per some other research I've done trying to get Electron to even start within my NixOS environment (development only, I haven't even built the application yet), npm can't be used to install electron and, in fact, causes an ENOENT error whenever you simply run npm i followed by electron .. The fix for this is to delete /node_modules/bin/electron (i've started renaming to .old so I can resume quickly from my Windows dev environment) and instead run nix-shell -p electron to temporarily expose the electron packages to PATH and allow the application to run.
This process works great... until I came across needing Widevine support. I've tried using electron's documented "solution" of running the app with the command-line flags to no avail, as well as editing the ELECTRON_MIRROR and ELECTRON_CUSTOM_URL environment variables to point to the above releases, but the end-all seems to be electron's issue with running within NixOS in general.
I'm at a bit of a loss here, and I'm not sure where else to start looking. When trying to use the documented components.whenReady() event, I'm greeted with an error that components is undefined (the error technically says that it can't read the property whenReady() of undefined).
I'm at the point where I'm considering distro-hopping to solve this issue. Please let me know what, if anything, I can provide to help get to the bottom of this, whatever that looks like.
Thanks in advance!

It is hard to get any feel for the problem from this information, and in general we don't really have the resources in this project to test the various Linux distros available. We have had reports of issues in some of them before, but this seems like something else - at least on the surface.

The fix for this is to delete /node_modules/bin/electron (i've started renaming to .old so I can resume quickly from my Windows dev environment) and instead run nix-shell -p electron to temporarily expose the electron packages to PATH and allow the application to run.

Are you sharing the same working copy on both Windows and Linux? If so, I'd say this is quirky and likely to cause some headaches. If you are doing this, I'd start by trying to use a clean Linux-only working copy on NixOS.

When trying to use the documented components.whenReady() event, I'm greeted with an error that components is undefined (the error technically says that it can't read the property whenReady() of undefined).

This seems to hint at one of two things. Either you are not actually using ECS at all (this can happen, check the node_modules/electron/dist/version file for the version used) or you are not importing the components API.

This is starting to feel more and more like a perfect storm. I've spent all of today exploring Nix's options for allowing this to work (overlays, package overrides, yarn2nix/nixfromnpm) that are falling apart due most likely to my own lack of familiarity with the operating system to that level.

Are you sharing the same working copy on both Windows and Linux? If so, I'd say this is quirky and likely to cause some headaches.

I am; that's why I've been renaming /bin/electron to /bin/electron.old and then simply renaming the package before updating my NPM packages back on my Windows machine, and the inverse on my NixOS machine. Regarding the pure Linux dev environment, that's essentially where I'm at right now. I'm out of town for the American holidays and only have my laptop, which is my NixOS environment. I haven't ran back to Windows to even test ECS over there as I simply haven't had access to it.

or you are not importing the components API.

I am; it shows components as being of type Electron.Components in the VSCode tooltip, and node_modules/electron/dist/version has 26.6.0+wvcus within it. In fact, I commented most of my main.js as a test and replaced my code with that provided in the #Using section, with no result. For fun, here's the current state:

const createWindow = () => {
    const win = new BrowserWindow({
        width: 800,
        height: 600,
        webPreferences: {
            nodeIntegration: true,
            plugins: true
        }
    })
    win.loadURL("http://localhost:3000")
    // widevine testing url:
    // win.loadURL("https://shaka-player-demo.appspot.com/")
    win.webContents.openDevTools()
}

// app.commandLine.appendSwitch('widevine-cdm-path', '../cdm/linux/')
// app.commandLine.appendSwitch('widevine-cdm-path', '/nix/store/mcanzi7lsnz8gk4r50sdkqdy5k85niih-google-chrome-119.0.6045.123/share/google/chrome/WidevineCdm/_platform_specific/linux_x64/libwidevinecdm.so')
// app.commandLine.appendSwitch('widevine-cdm-version', '4.10.2710.0')

app.whenReady().then(async () => {
  await components.whenReady();
  console.log('components ready:', components.status());
  createWindow();
});

As stated previous I am still looking at exploring Nix's inbuilt options to deal with this situation (overlays seem the most promising but I'm running into my own errors on that front) but just in case someone knew something that I didn't, I wanted to fire an issue over here.
All of this being said I'm fairly certain it has more to do with NixOS than ECS. Let me know if you have any other ideas before closing this one out, but my expectations are dwindling quickly. If I come up with a solution for this, I'll throw it up here under this issue just in case someone has this issue in the future and try to pay it forward!

Gave up on NixOS. Closing this due to current irrelevance.
If anyone comes across this, check out nix-ld. I wasn't willing to sacrifice the 'purity' of NixOS but that seemed to be as close as I was going to get.
Thanks for your help!


Closes #316 (Was dropping rest of proof)

Added test for existance + fix bad connection choice and… bad drop of rest_if_proof
I think this is a full fix, but to be honest I am not sure exactly how everything works, so I hope I am not breaking anything.
cargo test passes, and I did run make, but couldn't run with features="lp".

This PR seems to be overlooked... @oflatt maybe you could take a look?

@eytans would love to merge this if you have time to fix a small conflict!

@oflatt Sure. You can merge now


Versionname

May you prepare a fix for this please?

I just noticed that the strings for About and Settings are hard-coded in the menu. Can you fix that too please?

Het Marvin,
Yes i think thats no great think. We are going home today so I can do this
next week
Marcus
Mein Krebstagebuch: https://www.marcusradisch.de
CrazyMarvin @.***> schrieb am Sa., 13. Aug. 2022, 00:51:

I just noticed that the strings for About and Settings are hard-coded
in the menu. Can you fix that too please?
—
Reply to this email directly, view it on GitHub
https://github.com/Crazy-Marvin/VacationDays/issues/74#issuecomment-1213574299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFP5PLV3PR3BOIB3MP57WDVY3IQ5ANCNFSM56MK6DYA
.
You are receiving this because you were assigned.Message ID:
@.***>

  @SuppressLint({"StringFormatInvalid", "LocalSuppress"}) String version =                 String.format(getResources().getString(R.string.version),                 BuildConfig.VERSION_NAME);         appVersion.setText(version);
Does anyone have an idea why I see 1.0 instead of 7.0. In the build.gradle under Version_Name it says "7.0".
Does anyone have an idea why I see 1.0 instead of 7.0. In the build.gradle under Version_Name it says "7.0".

In my app the pancake counter it runs error free since the first version

  @SuppressLint({"StringFormatInvalid", "LocalSuppress"}) String version =                 String.format(getResources().getString(R.string.version),                 BuildConfig.VERSION_NAME);         appVersion.setText(version);
Does anyone have an idea why I see 1.0 instead of 7.0. In the build.gradle under Version_Name it says "7.0".
android {     compileSdkVersion 32     defaultConfig {         applicationId "rocks.poopjournal.vacationdays"         minSdkVersion 21         targetSdkVersion 31         versionCode 7         versionName "7.0"

I don't know. 😅
@arafaatqureshi, may you help us please?

In my app the pancake counter it runs error free since the first version

What do you mean, @amarradi? 🤔

I have adapted the code for the version display from my app on the vacationDays. But I see only version 1.0 but not 7.0 as defined in build.gradle
I'm sure there's another trap I don't know about. Actually the buildConfig.VERSION_NAME shows the versionName. At least that's what I thought. But it does not run.

Erm... You're importing a library's buildconfig instead of your app's.
import com.github.sundeepk.compactcalendarview.BuildConfig;
Just remove that line and rebuild the app (just to be sure) and the app will display the correct version.

@unbiaseduser
Thank you for your help. Now I have recovered from the monthly chemo and was able to adjust the source text accordingly. It runs. Thanks


[JavaFX - Part2] Change VBox to HBox

Current:
ImageView and Label are shown as nodes in a VBox

Problem:
According to the mockup screenshot, the ImageView and Label are in a HBox which forms the DialogBox, and the DialogBoxes are stacked in a VBox as the content of the ScrollPane.
Proposed:
Under the "VBox" node, we should have:
HBox -> VBox
ImageView -> HBox
Label -> HBox

@laney0808 What about the code given? Does it match the diagram or the mockup?

@laney0808 What about the code given? Does it match the diagram or the mockup?

Hi Prof! The code given does not seem to match the diagram or the mock up completely. The code for this part is only as detailed as the VBox (dialog container). It did not have dialog box (with HBox, ImageView, and Label). In the proposed version in #28, I already fixed the code by adding a sample dialog box. All that's left for this part is just to add a HBox as a container of ImageView and Label.

@laney0808 What about the code given? Does it match the diagram or the mockup?

Hi Prof! The code given does not seem to match the diagram or the mock up completely. The code for this part is only as detailed as the VBox (dialog container). It did not have dialog box (with HBox, ImageView, and Label). In the proposed version in #28, I already fixed the code by adding a sample dialog box. All that's left for this part is just to add a HBox as a container of ImageView and Label.

fixed by #70

fixed by #70


Why do many of the hooks require react experimental?

Why do many of the hooks require react experimental? That seems odd. For a useKeypress? it's a keypress. why?

Because they rely on useEffectEvent, which is itself only included in the experimental release of React at time of writing. I'm not a frontend dev by trade so I haven't done the reading around why this particular hook is used, but I presume a workaround without it is either error prone or just messy.


Please Add some Demo Exapmple

Please Provide some Demo Examples.

Duplicate of #21. I just noticed somebody already shared a working example in that thread, which is now linked to from the readme. I hope that helps you.

@Treora
thanks but I'm looking for the example where we can dispatch async actions along with query sync.


Animation tooltip

Hello, your plugin is very useful but i think that it will be nicest if we can choice other animation (why not use CSS3 animation ... for this moment only fade effect). Many plugin work with several choice of animation in CSS3 and if browser doesn't support CSS3 animation, use alternative jquery method.
So, my question is, have you planned to do this development ?
(I'm french, sorry for my bad english :S)

Hello,
Thank you for using my plugin.
In the next release of the plugin I will add css3 animation effects for sure.
:)

When is this next release :) ? (when i talked about other plugin, i give you an example http://ned.im/noty/#/about)

New version 1.0.2 is out.
There are css3 animation effects for showing/hiding the tooltip.
Check it out [here] (http://tipso.object505.com/) :)

Oww yes ! Just a question, for checking CSS3 animation support i have seen that you only check if it's IE <= 9 but i don't believe that just IE <= 9 don't support CSS3 animation. Check this link


RCLONE move complete Directory ?

Hello Guys,
i have the Version V.1.37 from rclone for Linux.
Now i would like to move a complete directory with all files and structure to google Drive .
The Directory called Muster with Files
Muster   (Directory)
+--------- TestFile.txt   (File)
+-------------File.txt   (File)
my command : rclone move -v /path/to/Muster remote:/Here
If i make this rclone move only the file testfile.txt and file.txt not the complete directory.
I Also make the following commands :
rclone copy Muster remote:
rclone copy /path/to/Muster remote:
rclone move Muster remote:/Directory
etc. etc. etc.
Every Command i give,  they only copy or move the files from Muster to drive they dont copy or move the complete directory Muster

Just name the destination directory like this
rclone copy -v /path/to/Muster remote:Muster


manually install a module developed

Problem
was developing extensions and the same work, I began to develop modules, took the example of google analytics and tried to manually put the package folder, but it does not work, how do I install it manually, and the Analystics folder inside package?

The composer.json and index.php must be present inside of your extension folder.

installed manually when I click request code , it returns the error that is in the image.

I noticed that when you install manually, it does not update the dependencies automatically and does not generate the Lusitanian folder , which is out of / packages / pagekit not just include the analytics folder inside / packages / pagekit , must have some command to update and seek the dependencies that the module needs and then installing the module , could you help me?
If you have any command via composer to manually install this module, after he was in the packages folder / pagekit ?
Help me :)

We have a Command for this.


Always round GPU layer dimensions to physical pixel boundaries

Fixes #13361
Fixes #15180
Fixes #15257
Fixes #14237
Fixes #14898
This ensure subpixel anti-aliasing works when window.devicePixelRatio is not an integer. Since subpixel anti-aliasing relies on the physical characteristics of the display, Chromium only enables it when rasterizing content that it knows will be aligned to a physical pixel boundary.
@50Wliu @ungb @Ben3eeE: can you give this a spin on Windows, please? We have tested it works correctly with 125% on Windows and by manually calling setZoomLevel on macOS in the console, but we'd like to make sure this is a holistic solution to the blurriness problem. Also, if you think this fixes more issues than the ones we have linked above, feel free to add them.
/cc: @atom/maintainers
🍐'd with @nathansobo.

Taking a 👀

Building now!

Everything looks :100:.
After this PR I think the only elements that don't have subpixel antialiasing are the tabs and status bar :tada:.

I noticed a slight blur before and saw that things are looking better after changing the display to 125% and 150%  thanks @50Wliu for verifying as well! 👍 💯

❤ 💯 👏 🚢 Amazing work @as-cii @nathansobo
I'll give this a quick test on Windows 7 tomorrow as well.

AppVeyor looks like it got stuck installing dependencies for the 32 bit build, which we don't even run tests on. Everything else was green. Merging.

Any idea when this will be released in a stable build?

@yonimend We can't guarantee anything but this is currently slated to ship with v1.21.0.

This will be contained in the next hotfix releases, which should go out this week.


⚠ GitLab Server has degraded performance

In 7ffee60, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 8787 ms

Resolved: GitLab Server performance has improved in c04c8d9.


Cannot Run on iOS Simulator or Device - Deploys App but Doesn't Start Due To Library not loaded: @rpath/AppAuth.framework/AppAuth

Steps to reproduce
Hello,
Firstly apologies - completely lost track of the ticket and it was closed - https://github.com/leancodepl/patrol/issues/2263
Just to clarify, it works absolutely fine when my Android device is connected so this is exclusively an iOS bug. I've been through the steps to setup quite a few times but nothing seems to change. My app also builds on both devices no issue and both flavors.
Run test release for iOS:
patrol test --release --flavor Dev --verbose
• Building app with entrypoint test_bundle.dart for iOS device (release)...
✓ Completed building app with entrypoint test_bundle.dart for iOS device (60.6s)
• Running app with entrypoint test_bundle.dart for iOS device on device Peter’s iPhone...

Actual results
I see the RunnerTests being moved onto the device but it never opens/runs. I've followed this: https://github.com/leancodepl/patrol/issues/1441 link and get the same result even if I type the commands individually.
Based on some of the logs it seems to be deciding that it's a simulator? I'm really not sure but the iOS versions in my XCode are matching and 14.0...
I've had a look at the ticket https://github.com/leancodepl/patrol/issues/2003#issuecomment-2135325785 that was proposed as a work around but I cannot install 14.3 xcode CLI as the version is too old.
Logs

Logs
```
Verbose mode enabled. More logs will be printed.
Received 1 test target(s)
Received test target: /Users/user1/Development/test/test/integration_test/app_test.dart
Generated entrypoint /Users/user1/Development/test/test/integration_test/test_bundle.dart with 1 bundled test(s)
Received iOS flavor: Dev
Received 5 --dart-define(s) (0 custom, 5 internal)
Received internal --dart-define: PATROL_WAIT=0
Received internal --dart-define: PATROL_TEST_LABEL_ENABLED=true
Received internal --dart-define: INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false
Received internal --dart-define: PATROL_TEST_SERVER_PORT=8081
Received internal --dart-define: PATROL_APP_SERVER_PORT=8082
• Building app with entrypoint test_bundle.dart for iOS device (release)...
$ flutter build ios --no-version-check --suppress-analytics --config-only --no-codesign --release --flavor Dev --target /Users/user1/Development/test/test/integration_test/test_bundle.dart --dart-define PATROL_WAIT=0 --dart-define PATROL_TEST_LABEL_ENABLED=true --dart-define INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false --dart-define PATROL_TEST_SERVER_PORT=8081 --dart-define PATROL_APP_SERVER_PORT=8082
        Warning: Building for device with codesigning disabled. You will have to manually codesign before deploying to device.
        Building com.test.dev for device (ios-release)...
$ xcodebuild build-for-testing -workspace Runner.xcworkspace -scheme Dev -configuration Release-Dev -sdk iphoneos -destination generic/platform=iOS -quiet -derivedDataPath ../build/ios_integ OTHER_SWIFT_FLAGS=$(inherited) -D PATROL_ENABLED
        /Users/user1/Development/test/test/ios/Runner/AppDelegate.swift:14:9: warning: initialization of immutable value 'methodChannel' was never used; consider replacing with assignment to '_' or removing it
            let methodChannel = FlutterMethodChannel(name: "com.test.test/maps", binaryMessenger: flutterViewController.binaryMessenger)
            ~~~~^~~~~~~~~~~~~
            _
        ld: warning: no platform load command found in '/Users/user1/Development/test/test/ios/Pods/MLKitBarcodeScanning/Frameworks/MLKitBarcodeScanning.framework/MLKitBarcodeScanning', assuming: iOS
        ld: warning: no platform load command found in '/Users/user1/Development/test/test/ios/Pods/MLKitBarcodeScanning/Frameworks/MLKitBarcodeScanning.framework/MLKitBarcodeScanning', assuming: iOS
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'AppAuth-AppAuthCore_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'AppAuth' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'CocoaAsyncSocket' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'PromisesObjC-FBLPromises_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'PromisesObjC' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseAppCheckInterop' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleUtilities-GoogleUtilities_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleUtilities' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseCoreInternal-FirebaseCoreInternal_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseCoreInternal' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseCore-FirebaseCore_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseCore' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GTMSessionFetcher-GTMSessionFetcher_Core_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GTMSessionFetcher-GTMSessionFetcher_Full_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GTMSessionFetcher' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'RecaptchaInterop' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseAuth-FirebaseAuth_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseAuth' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseInstallations-FirebaseInstallations_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseInstallations' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'nanopb-nanopb_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'nanopb' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleDataTransport-GoogleDataTransport_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleDataTransport' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseMessaging-FirebaseMessaging_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'FirebaseMessaging' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GTMAppAuth-GTMAppAuth_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GTMAppAuth' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleToolboxForMac-GoogleToolboxForMac_Logger_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleToolboxForMac-GoogleToolboxForMac_Privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleToolboxForMac' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'flutter_native_splash-flutter_native_splash_privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'patrol-patrol_privacy' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'wakelock_plus-thermal' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleUtilitiesComponents' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleSignIn-GoogleSignIn' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'GoogleSignIn' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'permission_handler_apple-permission_handler_apple_privacy' from project 'Pods')
        note: Run script build phase 'Run Script' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
        note: Run script build phase 'Copyy g services file' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
        note: Run script build phase 'Thin Binary' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
        warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
        warning: Run script build phase 'xcode_backend build' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RunnerUITests' from project 'Runner')
        warning: Run script build phase 'xcode_backend embed_and_thin' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RunnerUITests' from project 'Runner')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'VeriffSDK' from project 'Pods')
        /Users/user1/Development/test/test/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.5.99. (in target 'Firebase' from project 'Pods')
✓ Completed building app with entrypoint test_bundle.dart for iOS device (68.2s)
build/ios_integ/Build/Products/Release-iphoneos/Runner.app (app under test)
build/ios_integ/Build/Products/Release-iphoneos/RunnerUITests-Runner.app (test instrumentation app)
$ xcodebuild -showsdks -json
Assuming SDK version 17.5 for iphonesimulator
Looking for .xctestrun matching Dev_*iphoneos17.5*.xctestrun at build/ios_integ/Build/Products
Found 1 match(es), the first one will be used
Found /Users/user1/Development/test/test/build/ios_integ/Build/Products/Dev_Dev_iphoneos17.5-arm64.xctestrun
build/ios_integ/Build/Products/Dev_Dev_iphoneos17.5-arm64.xctestrun (xctestrun file)
user1@Peters-MBP test % patrol test --release --flavor Dev
No device specified, using the first one (iPhone)
• Building app with entrypoint test_bundle.dart for iOS device (release)...
✓ Completed building app with entrypoint test_bundle.dart for iOS device (76.7s)
• Running app with entrypoint test_bundle.dart for iOS device on device iPhone...
        2024-08-12 19:06:01.968 xcodebuild[4840:6995318] [MT] IDETestOperationsObserverDebug: 11.285 elapsed -- Testing started completed.
        2024-08-12 19:06:01.968 xcodebuild[4840:6995318] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
        2024-08-12 19:06:01.968 xcodebuild[4840:6995318] [MT] IDETestOperationsObserverDebug: 11.285 sec, +11.285 sec -- end
        Testing failed:
                RunnerUITests-Runner (790) encountered an error (Failed to load the test bundle. (Underlying Error: The bundle “RunnerUITests” couldn’t be loaded. The bundle couldn’t be loaded. Try reinstalling the bundle. dlopen(/var/containers/Bundle/Application/072C3EBF-E7B3-4CAD-90BF-12EF866B727F/RunnerUITests-Runner.app/PlugIns/RunnerUITests.xctest/RunnerUITests, 0x0109): Library not loaded: @rpath/AppAuth.framework/AppAuth
          Referenced from: <960250C3-0B4C-3680-89C6-64CAEF3747A6> /private/var/containers/Bundle/Application/072C3EBF-E7B3-4CAD-90BF-12EF866B727F/RunnerUITests-Runner.app/PlugIns/RunnerUITests.xctest/RunnerUITests
          Reason: tried: '/System/Developer/Library/Frameworks/AppAuth.framework/AppAuth' (no such file), '/private/var/containers/Bundle/Application/072C3EBF-E7B3-4CAD-90BF-12EF866B727F/RunnerUITests-Runner.app/PlugIns/RunnerUITests.xctest/Frameworks/AppAuth.framework/AppAuth' (no such file), '/usr/lib/swift/AppAuth.framework/AppAuth' (no such file, not in dyld cache), '/private/preboot/Cryptexes/OS/usr/lib/swift/AppAuth.framework/AppAuth' (no such file), '/private/var/containers/Bundle/Application/072C3EBF-E7B3-4CAD-90BF-12EF866B727F/RunnerUITests-Runner.app/Frameworks/AppAuth.framework/AppAuth' (no such file), '/private/var/containers/Bundle/Application/072C3EBF-E7B3-4CAD-90BF-12EF866B727F/RunnerUITests-Runner.app/PlugIns/RunnerUITests.xctest/Frameworks/AppAuth.framework/AppAuth' (no such file), '/usr/lib/swift/AppAuth.framework/AppAuth' (no such file, not in dyld cache), '/private/preboot/Cryptexes/OS/usr/lib/swift/AppAuth.framework/AppAuth' (no such file), '/private/var/containers/Bundle/Application/072C3EBF-E7B3-4CAD-90BF-12EF866B727F/RunnerUITests-Runner.app/Frameworks/AppAuth.framework/AppAuth' (no such file), '/private/var/containers/Bundle/Application/072C3EBF-E7B3-4CAD-90BF-12EF866B727F/RunnerUITests-Runner.app/Frameworks/AppAuth.framework/AppAuth' (no such file), '/System/Developer/Library/Frameworks/AppAuth.framework/AppAuth' (no such file), '/private/preboot/Cryptexes/OS/System/Developer/Library/Frameworks/AppAuth.framework/AppAuth' (no such file), '/System/Developer/usr/lib/AppAuth.framework/AppAuth' (no such file), '/private/preboot/Cryptexes/OS/System/Developer/usr/lib/AppAuth.framework/AppAuth' (no such file), '/Developer/Library/Frameworks/AppAuth.framework/AppAuth' (no such file), '/private/preboot/Cryptexes/OS/Developer/Library/Frameworks/AppAuth.framework/AppAuth' (no such file), '/Developer/usr/lib/AppAuth.framework/AppAuth' (no such file), '/private/preboot/Cryptexes/OS/Developer/usr/lib/AppAuth.framework/AppAuth' (no such file)))
    ** TEST EXECUTE FAILED **

✗ Failed to execute tests of app with entrypoint test_bundle.dart for iOS device on device iPhone (xcodebuild exited with code 65) (14.5s)
Error: xcodebuild exited with code 65
See the logs above to learn what happened. Also consider running with --verbose. If the logs still aren't useful, then it's a bug - please report it.

Patrol version
Patrol Package ^3.9.0
Tried with 2.6.0, 2.8.0 and 3.0.0
Patrol Doctor output

Patrol Doctor output
Patrol CLI version: 3.1.0
Flutter command: flutter
  Flutter 3.22.2 • channel stable
Android:
• Program adb found in /Users/user1/Library/Android/sdk/platform-tools/adb
• Env var $ANDROID_HOME set to /Users/user1/Library/Android/sdk/platform-tools
iOS / macOS:
• Program xcodebuild found in /usr/bin/xcodebuild
• Program ideviceinstaller found in /opt/homebrew/bin/ideviceinstaller

Flutter Doctor output

Flutter Doctor output
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79 darwin-arm64 (Rosetta), locale en-DE)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.92.0)
[✓] Connected device (4 available)
[✓] Network resources

! Doctor found issues in 1 category.

Hi @pma07pg!
About the workaround you linked - you can install older xcode just to build the app. I use a tool called xcodes for that and it works (I'm on macOS 14).
If this doesn't help - please provide a project, where this error is reproducible, so we can investigate by ourselves. It may have something to do with AppAuth and Patrol being used together, in such case we need a reproducible example.

Will give this a go! Thanks!

Hi @jBorkowska I've just installed xcodes and installed xcode 14.3.1. However when I try to open it, it tells me that it's incompatible and needs to be updated...  I'm currently using Sonoma 14.5.
Thanks!

Yes, but you don't have to open it. If you choose the older one in xcodes select command, patrol will use command-line tools from that older version

OK so I managed to get the xcodes stuff working and changed the app_options file to select 'iOS' only, as I only want to test it on my physical device and I get these errors:
patrol build ios --release --flavor Dev --verbose
Verbose mode enabled. More logs will be printed.
Received 1 test target(s)
Received test target: /Users/user/Development/test1/test1/integration_test/app_test.dart
Generated entrypoint /Users/user/Development/test1/test1/integration_test/test_bundle.dart with 1 bundled test(s)
Received iOS flavor: Dev
Received 5 --dart-define(s) (0 custom, 5 internal)
Received internal --dart-define: PATROL_WAIT=0
Received internal --dart-define: PATROL_TEST_LABEL_ENABLED=true
Received internal --dart-define: INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false
Received internal --dart-define: PATROL_TEST_SERVER_PORT=8081
Received internal --dart-define: PATROL_APP_SERVER_PORT=8082
• Building app with entrypoint test_bundle.dart for iOS device (release)...
$ flutter build ios --no-version-check --suppress-analytics --config-only --no-codesign --release --flavor Dev --target /Users/user/Development/test1/test1/integration_test/test_bundle.dart --dart-define PATROL_WAIT=0 --dart-define PATROL_TEST_LABEL_ENABLED=true --dart-define INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false --dart-define PATROL_TEST_SERVER_PORT=8081 --dart-define PATROL_APP_SERVER_PORT=8082
	Warning: Building for device with codesigning disabled. You will have to manually codesign before deploying to device.
	Building com.test1.dev for device (ios-release)...
$ xcodebuild build-for-testing -workspace Runner.xcworkspace -scheme Dev -configuration Release-Dev -sdk iphoneos -destination generic/platform=iOS -quiet -derivedDataPath ../build/ios_integ OTHER_SWIFT_FLAGS=$(inherited) -D PATROL_ENABLED
	2024-08-14 17:52:35.883 xcodebuild[14391:950389] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
	2024-08-14 17:52:36.921 xcodebuild[14391:950421]  iPhoneConnect: 📱<DVTiOSDevice (0x7f97063d17c0), iPhone, iPhone, 17.5.1 (21F90), 00008110-001C79C42108401E> unable to mount developer disk image, (Error Domain=com.apple.dt.DVTDeviceSupportFilesDDIError Code=2 "Could not locate device support files" UserInfo={NSLocalizedDescription=Could not locate device support files, NSLocalizedRecoverySuggestion=You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com.

	[missing string: 869a8e318f07f3e2f42e11d435502286094f76de], DVTRadarComponentKey=487927, DeviceType=iPhone14,6, NSLocalizedFailureReason=The device may be running a version of iOS (17.5.1 21F90) that is not supported by this version of Xcode.}) {
	    DVTRadarComponentKey = 487927;
	    DeviceType = "iPhone14,6";
	    NSLocalizedDescription = "Could not locate device support files";
	    NSLocalizedFailureReason = "The device may be running a version of iOS (17.5.1 21F90) that is not supported by this version of Xcode.";
	    NSLocalizedRecoverySuggestion = "You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com.\n\n[missing string: 869a8e318f07f3e2f42e11d435502286094f76de]";
	}
	2024-08-14 17:52:36.962 xcodebuild[14391:950389] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x7f97063d17c0), iPhone, iPhone, 17.5.1 (21F90), 00008110-001C79C42108401E> -- An error occurred whilst preparing device for development -- Could not locate device support files
	Domain: com.apple.dt.DVTDeviceSupportFilesDDIError
	Code: 2
	Failure Reason: The device may be running a version of iOS (17.5.1 21F90) that is not supported by this version of Xcode.
	Recovery Suggestion: You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com.

	[missing string: 869a8e318f07f3e2f42e11d435502286094f76de]
	User Info: {
	    DVTRadarComponentKey = 487927;
	    DeviceType = "iPhone14,6";
	}
	--
	2024-08-14 17:52:36.962 xcodebuild[14391:950389] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x7f97063d17c0), iPhone, iPhone, 17.5.1 (21F90), 00008110-001C79C42108401E> == Underlying device preparation errors ==
	2024-08-14 17:52:36.962 xcodebuild[14391:950389] [MT] iPhoneConnect: Could not locate device support files
	Domain: com.apple.dt.DVTDeviceSupportFilesDDIError
	Code: 2
	Failure Reason: The device may be running a version of iOS (17.5.1 21F90) that is not supported by this version of Xcode.
	Recovery Suggestion: You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com.

	[missing string: 869a8e318f07f3e2f42e11d435502286094f76de]
	User Info: {
	    DVTRadarComponentKey = 487927;
	    DeviceType = "iPhone14,6";
	}
	--
	2024-08-14 17:52:36.962 xcodebuild[14391:950389] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x7f97063d17c0), iPhone, iPhone, 17.5.1 (21F90), 00008110-001C79C42108401E> == END: Underlying device preparation errors ==
	2024-08-14 17:52:36.968 xcodebuild[14391:950421]  iPhoneConnect: 📱<DVTiOSDevice (0x7f97063d17c0), iPhone, iPhone, 17.5.1 (21F90), 00008110-001C79C42108401E> unable to mount developer disk image, (Error Domain=com.apple.dt.DVTDeviceSupportFilesDDIError Code=2 "Could not locate device support files" UserInfo={NSLocalizedDescription=Could not locate device support files, NSLocalizedRecoverySuggestion=You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com.

	[missing string: 869a8e318f07f3e2f42e11d435502286094f76de], DVTRadarComponentKey=487927, DeviceType=iPhone14,6, NSLocalizedFailureReason=The device may be running a version of iOS (17.5.1 21F90) that is not supported by this version of Xcode.}) {
	    DVTRadarComponentKey = 487927;
	    DeviceType = "iPhone14,6";
	    NSLocalizedDescription = "Could not locate device support files";
	    NSLocalizedFailureReason = "The device may be running a version of iOS (17.5.1 21F90) that is not supported by this version of Xcode.";
	    NSLocalizedRecoverySuggestion = "You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com.\n\n[missing string: 869a8e318f07f3e2f42e11d435502286094f76de]";
	}
	2024-08-14 17:52:36.968 xcodebuild[14391:950389] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x7f97063d17c0), iPhone, iPhone, 17.5.1 (21F90), 00008110-001C79C42108401E> -- An error occurred whilst preparing device for development -- Could not locate device support files
	Domain: com.apple.dt.DVTDeviceSupportFilesDDIError
	Code: 2
	Failure Reason: The device may be running a version of iOS (17.5.1 21F90) that is not supported by this version of Xcode.
	Recovery Suggestion: You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com.

	[missing string: 869a8e318f07f3e2f42e11d435502286094f76de]
	User Info: {
	    DVTRadarComponentKey = 487927;
	    DeviceType = "iPhone14,6";
	}
	--
	2024-08-14 17:52:36.968 xcodebuild[14391:950389] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x7f97063d17c0), iPhone, iPhone, 17.5.1 (21F90), 00008110-001C79C42108401E> == Underlying device preparation errors ==
	2024-08-14 17:52:36.968 xcodebuild[14391:950389] [MT] iPhoneConnect: Could not locate device support files
	Domain: com.apple.dt.DVTDeviceSupportFilesDDIError
	Code: 2
	Failure Reason: The device may be running a version of iOS (17.5.1 21F90) that is not supported by this version of Xcode.
	Recovery Suggestion: You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com.

	[missing string: 869a8e318f07f3e2f42e11d435502286094f76de]
	User Info: {
	    DVTRadarComponentKey = 487927;
	    DeviceType = "iPhone14,6";
	}
	--
	2024-08-14 17:52:36.968 xcodebuild[14391:950389] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x7f97063d17c0), iPhone, iPhone, 17.5.1 (21F90), 00008110-001C79C42108401E> == END: Underlying device preparation errors ==
	2024-08-14 17:52:49.195 xcodebuild[14391:950433]  DVTPortal: Service '<DVTPortalViewDeveloperService: 0x600000c98bc0; action='viewDeveloper'>' encountered an unexpected result code from the portal ('1100')
	2024-08-14 17:52:49.196 xcodebuild[14391:950433]  DVTPortal: Error:
	Error Domain=DVTPortalServiceErrorDomain Code=1100 "Your session has expired. Please log in." UserInfo={payload={
	    creationTimestamp = "2024-08-14T15:52:49Z";
	    httpCode = 200;
	    protocolVersion = QH65B2;
	    requestUrl = "https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action";
	    responseId = "796af603-dec3-4744-87f8-b29d66eaef58";
	    resultCode = 1100;
	    resultString = "Your session has expired. Please log in.";
	    userLocale = "en_US";
	    userString = "Your session has expired. Please log in.";
	}, NSLocalizedDescription=Your session has expired. Please log in.}
	2024-08-14 17:52:49.370 xcodebuild[14391:950421]  DVTPortal: Service '<DVTPortalViewDeveloperService: 0x600000c83380; action='viewDeveloper'>' encountered an unexpected result code from the portal ('1100')
	2024-08-14 17:52:49.370 xcodebuild[14391:950421]  DVTPortal: Error:
	Error Domain=DVTPortalServiceErrorDomain Code=1100 "Your session has expired. Please log in." UserInfo={payload={
	    creationTimestamp = "2024-08-14T15:52:49Z";
	    httpCode = 200;
	    protocolVersion = QH65B2;
	    requestUrl = "https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action";
	    responseId = "68a55953-984b-46ab-a7e9-5d90a28ef28c";
	    resultCode = 1100;
	    resultString = "Your session has expired. Please log in.";
	    userLocale = "en_US";
	    userString = "Your session has expired. Please log in.";
	}, NSLocalizedDescription=Your session has expired. Please log in.}
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/Analytics/AnalyticLoggableError.swift:59:39: warning: expression of type 'String' is unused
	                analyticLoggableError.analyticsErrorType
	                ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/Analytics/AnalyticLoggableError.swift:61:22: warning: result of call to 'extractErrorType(from:)' is unused
	                Self.extractErrorType(from: self)
	                     ^               ~~~~~~~~~~~~
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/Analytics/AnalyticLoggableError.swift:66:39: warning: expression of type 'String' is unused
	                analyticLoggableError.analyticsErrorCode
	                ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/Analytics/AnalyticLoggableError.swift:68:22: warning: result of call to 'extractErrorCode(from:)' is unused
	                Self.extractErrorCode(from: self)
	                     ^               ~~~~~~~~~~~~
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/API Bindings/StripeError.swift:32:13: warning: string literal is unused
	            "invalidRequest"
	            ^~~~~~~~~~~~~~~~
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/API Bindings/StripeError.swift:34:33: warning: result of operator '??' is unused
	            stripeAPIError.code ?? ""
	            ~~~~~~~~~~~~~~~~~~~ ^  ~~
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/Analytics/AnalyticLoggableError.swift:63:9: error: missing return in closure expected to return 'String'
	        }()
	        ^
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/API Bindings/StripeError.swift:36:5: error: missing return in getter expected to return 'String'
	    }
	    ^
	/Users/user/Development/test1/test1/ios/Pods/StripeCore/StripeCore/StripeCore/Source/Analytics/AnalyticLoggableError.swift:70:9: error: missing return in closure expected to return 'String'
	        }()
	        ^
	In file included from /Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/SquareInAppPaymentsFlutterPlugin.m:19:
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.h:23:53: warning: pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified) [-Wnullability-completeness]
	- (void)initWithMethodChannel:(FlutterMethodChannel *)channel;
	                                                    ^
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.h:23:53: note: insert '_Nullable' if the pointer may be null
	- (void)initWithMethodChannel:(FlutterMethodChannel *)channel;
	                                                    ^
	                                                     _Nullable
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.h:23:53: note: insert '_Nonnull' if the pointer should never be null
	- (void)initWithMethodChannel:(FlutterMethodChannel *)channel;
	                                                    ^
	                                                     _Nonnull
	1 warning generated.
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPSecureRemoteCommerce.m:37:76: warning: 'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
	    UIViewController *rootViewController = UIApplication.sharedApplication.keyWindow.rootViewController;
	                                                                           ^
	In module 'UIKit' imported from /Users/user/Development/test1/test1/ios/Pods/Target Support Files/square_in_app_payments/square_in_app_payments-prefix.pch:2:
	/Applications/Xcode-14.3.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS16.4.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:135:51: note: 'keyWindow' has been explicitly marked deprecated here
	@property(nullable, nonatomic,readonly) UIWindow *keyWindow API_DEPRECATED("Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes", ios(2.0, 13.0));
	                                                  ^
	1 warning generated.
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPCardEntry.m:63:76: warning: 'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
	    UIViewController *rootViewController = UIApplication.sharedApplication.keyWindow.rootViewController;
	                                                                           ^
	In module 'UIKit' imported from /Users/user/Development/test1/test1/ios/Pods/Target Support Files/square_in_app_payments/square_in_app_payments-prefix.pch:2:
	/Applications/Xcode-14.3.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS16.4.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:135:51: note: 'keyWindow' has been explicitly marked deprecated here
	@property(nullable, nonatomic,readonly) UIWindow *keyWindow API_DEPRECATED("Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes", ios(2.0, 13.0));
	                                                  ^
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPCardEntry.m:87:76: warning: 'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
	    UIViewController *rootViewController = UIApplication.sharedApplication.keyWindow.rootViewController;
	                                                                           ^
	In module 'UIKit' imported from /Users/user/Development/test1/test1/ios/Pods/Target Support Files/square_in_app_payments/square_in_app_payments-prefix.pch:2:
	/Applications/Xcode-14.3.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS16.4.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:135:51: note: 'keyWindow' has been explicitly marked deprecated here
	@property(nullable, nonatomic,readonly) UIWindow *keyWindow API_DEPRECATED("Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes", ios(2.0, 13.0));
	                                                  ^
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPCardEntry.m:104:76: warning: 'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
	    UIViewController *rootViewController = UIApplication.sharedApplication.keyWindow.rootViewController;
	                                                                           ^
	In module 'UIKit' imported from /Users/user/Development/test1/test1/ios/Pods/Target Support Files/square_in_app_payments/square_in_app_payments-prefix.pch:2:
	/Applications/Xcode-14.3.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS16.4.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:135:51: note: 'keyWindow' has been explicitly marked deprecated here
	@property(nullable, nonatomic,readonly) UIWindow *keyWindow API_DEPRECATED("Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes", ios(2.0, 13.0));
	                                                  ^
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPCardEntry.m:131:76: warning: 'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
	    UIViewController *rootViewController = UIApplication.sharedApplication.keyWindow.rootViewController;
	                                                                           ^
	In module 'UIKit' imported from /Users/user/Development/test1/test1/ios/Pods/Target Support Files/square_in_app_payments/square_in_app_payments-prefix.pch:2:
	/Applications/Xcode-14.3.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS16.4.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:135:51: note: 'keyWindow' has been explicitly marked deprecated here
	@property(nullable, nonatomic,readonly) UIWindow *keyWindow API_DEPRECATED("Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes", ios(2.0, 13.0));
	                                                  ^
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPCardEntry.m:273:76: warning: 'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
	    UIViewController *rootViewController = UIApplication.sharedApplication.keyWindow.rootViewController;
	                                                                           ^
	In module 'UIKit' imported from /Users/user/Development/test1/test1/ios/Pods/Target Support Files/square_in_app_payments/square_in_app_payments-prefix.pch:2:
	/Applications/Xcode-14.3.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS16.4.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:135:51: note: 'keyWindow' has been explicitly marked deprecated here
	@property(nullable, nonatomic,readonly) UIWindow *keyWindow API_DEPRECATED("Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes", ios(2.0, 13.0));
	                                                  ^
	5 warnings generated.
	In file included from /Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.m:17:
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.h:23:53: warning: pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified) [-Wnullability-completeness]
	- (void)initWithMethodChannel:(FlutterMethodChannel *)channel;
	                                                    ^
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.h:23:53: note: insert '_Nullable' if the pointer may be null
	- (void)initWithMethodChannel:(FlutterMethodChannel *)channel;
	                                                    ^
	                                                     _Nullable
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.h:23:53: note: insert '_Nonnull' if the pointer should never be null
	- (void)initWithMethodChannel:(FlutterMethodChannel *)channel;
	                                                    ^
	                                                     _Nonnull
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.m:102:76: warning: 'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
	    UIViewController *rootViewController = UIApplication.sharedApplication.keyWindow.rootViewController;
	                                                                           ^
	In module 'UIKit' imported from /Users/user/Development/test1/test1/ios/Pods/Target Support Files/square_in_app_payments/square_in_app_payments-prefix.pch:2:
	/Applications/Xcode-14.3.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS16.4.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:135:51: note: 'keyWindow' has been explicitly marked deprecated here
	@property(nullable, nonatomic,readonly) UIWindow *keyWindow API_DEPRECATED("Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes", ios(2.0, 13.0));
	                                                  ^
	/Users/user/.pub-cache/hosted/pub.dev/square_in_app_payments-1.7.9/ios/Classes/FSQIPApplePay.m:160:76: warning: 'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
	    UIViewController *rootViewController = UIApplication.sharedApplication.keyWindow.rootViewController;
	                                                                           ^
	In module 'UIKit' imported from /Users/user/Development/test1/test1/ios/Pods/Target Support Files/square_in_app_payments/square_in_app_payments-prefix.pch:2:
	/Applications/Xcode-14.3.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS16.4.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:135:51: note: 'keyWindow' has been explicitly marked deprecated here
	@property(nullable, nonatomic,readonly) UIWindow *keyWindow API_DEPRECATED("Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes", ios(2.0, 13.0));
	                                                  ^
	3 warnings generated.
	ld: warning: dylib (/Users/user/Development/test1/test1/build/ios_integ/Build/Products/Release-Dev-iphoneos/XCFrameworkIntermediates/SquareBuyerVerificationSDK/SquareBuyerVerificationSDK.framework/SquareBuyerVerificationSDK) was built for newer iOS version (15.0) than being linked (14.0)
	ld: warning: dylib (/Users/user/Development/test1/test1/build/ios_integ/Build/Products/Release-Dev-iphoneos/XCFrameworkIntermediates/SquareInAppPaymentsSDK/SquareInAppPaymentsSDK.framework/SquareInAppPaymentsSDK) was built for newer iOS version (15.0) than being linked (14.0)
	note: Building targets in dependency order
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleUtilities-GoogleUtilities_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleUtilities' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GTMAppAuth-GTMAppAuth_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GTMAppAuth' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'permission_handler_apple-permission_handler_apple_privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'nanopb-nanopb_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'flutter_native_splash-flutter_native_splash_privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'PromisesObjC-FBLPromises_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleToolboxForMac-GoogleToolboxForMac_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleToolboxForMac-GoogleToolboxForMac_Logger_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GTMSessionFetcher-GTMSessionFetcher_Full_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'AppAuth-AppAuthCore_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GTMSessionFetcher-GTMSessionFetcher_Core_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'CocoaAsyncSocket' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'AppAuth' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'nanopb' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'FirebaseCore' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleSignIn' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleDataTransport' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'FirebaseInstallations' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleSignIn-GoogleSignIn' from project 'Pods')
	warning: Run script build phase 'xcode_backend embed_and_thin' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RunnerUITests' from project 'Runner')
	warning: Run script build phase 'xcode_backend build' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RunnerUITests' from project 'Runner')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'FirebaseInstallations-FirebaseInstallations_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'FirebaseCore-FirebaseCore_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleToolboxForMac' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'FirebaseCoreInternal-FirebaseCoreInternal_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleUtilitiesComponents' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'FirebaseCoreInternal' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'FirebaseAppCheckInterop' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GoogleDataTransport-GoogleDataTransport_Privacy' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'PromisesObjC' from project 'Pods')
	/Users/user/Development/test1/test1/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 11.0 to 16.4.99. (in target 'GTMSessionFetcher' from project 'Pods')
	note: Run script build phase 'Run Script' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
	note: Run script build phase 'Copyy g services file' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
	note: Run script build phase 'Thin Binary' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
	warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
	** TEST BUILD FAILED **

✗ Failed to build app with entrypoint test_bundle.dart for iOS device (xcodebuild exited with code 65) (42.3s)
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.build.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:137:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.build (package:patrol_cli/src/ios/ios_test_backend.dart:76:5)
<asynchronous suspension>
#4      BuildIOSCommand.run (package:patrol_cli/src/commands/build_ios.dart:163:7)
<asynchronous suspension>
#5      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#6      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:348:18)
<asynchronous suspension>
#7      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:292:18)
<asynchronous suspension>
#8      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:70:20)
<asynchronous suspension>
#9      main (file:///Users/user/.pub-cache/hosted/pub.dev/patrol_cli-3.1.0/bin/main.dart:6:20)
<asynchronous suspension>

See the logs above to learn what happened. Also consider running with --verbose. If the logs still aren't useful, then it's a bug - please report it.
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.build.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:137:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.build (package:patrol_cli/src/ios/ios_test_backend.dart:76:5)
<asynchronous suspension>
#4      BuildIOSCommand.run (package:patrol_cli/src/commands/build_ios.dart:163:7)
<asynchronous suspension>
#5      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#6      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:348:18)
<asynchronous suspension>
#7      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:292:18)
<asynchronous suspension>
#8      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:70:20)
<asynchronous suspension>
#9      main (file:///Users/user/.pub-cache/hosted/pub.dev/patrol_cli-3.1.0/bin/main.dart:6:20)
<asynchronous suspension>

Hi @pma07pg, sorry for very late response. Did you manage to fix this issue? About the last logs that you uploaded - I don't see anything patrol-related. Let us know if you still have some questions

No worries! Unfortunately it now doesn't seem to be working at all. I upgraded some packages in my pubspec and even on Android it's showing a Task :app:connectedDevDebugAndroidTest FAILED with nothing in the index.html. Very strange as there's absolutely nothing I'd changed in my setup. It's not working on my Windows machine or my Mac now so I assume there's some kind of dependency issue or something but the logs aren't giving much away...
       : > Task :app:dexBuilderDevDebugAndroidTest UP-TO-DATE
        : > Task :app:mergeProjectDexDevDebugAndroidTest UP-TO-DATE
        : > Task :app:packageDevDebugAndroidTest UP-TO-DATE
        : > Task :app:createDevDebugAndroidTestApkListingFileRedirect UP-TO-DATE
        : > Task :app:connectedDevDebugAndroidTest FAILED
        :
        : Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
        :
        : You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
        :
        : See https://docs.gradle.org/7.6/userguide/command_line_interface.html#sec:command_line_warnings
        : 510 actionable tasks: 6 executed, 504 up-to-date

        FAILURE: Build failed with an exception.

        * What went wrong:
        Execution failed for task ':app:connectedDevDebugAndroidTest'.
        See the report at: file:///Users/user/Development/test/test/build/app/reports/androidTests/connected/flavors/dev/index.html

        * Try:
        > Run with --stacktrace option to get the stack trace.
        > Run with --info or --debug option to get more log output.
        > Run with --scan to get full insights.

        * Get more help at https://help.gradle.org

        BUILD FAILED in 11s
✗ Failed to execute tests of apk with entrypoint test_bundle.dart on device 32131FDH200113 (Gradle test execution failed with code 1) (12.0s)
Exception: Gradle test execution failed with code 1
#0      AndroidTestBackend.execute.<anonymous closure> (package:patrol_cli/src/android/android_test_backend.dart:140:9)
<asynchronous suspension>
#1      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#2      AndroidTestBackend.execute (package:patrol_cli/src/android/android_test_backend.dart:106:5)
<asynchronous suspension>
#3      TestCommand._execute (package:patrol_cli/src/commands/test.dart:336:7)
<asynchronous suspension>
#4      TestCommand.run (package:patrol_cli/src/commands/test.dart:228:23)
<asynchronous suspension>
#5      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#6      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:348:18)
<asynchronous suspension>
#7      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:292:18)
<asynchronous suspension>
#8      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:70:20)
<asynchronous suspension>
#9      main (file:///Users/user/.pub-cache/hosted/pub.dev/patrol_cli-2.8.1/bin/main.dart:6:20)
<asynchronous suspension>

Very strange but after some further inspection I get this error:
SEVERE: Fatal error while executing main with args: --proto_config=/Users/user/.android/utp/runnerConfig16394222982918146376.pb --proto_server_config=/Users/user/.android/utp/serverConfig12969538524026250445.pb
java.lang.IllegalAccessError: class com.google.protobuf.GeneratedMessageV3 tried to access method 'boolean com.google.protobuf.CodedInputStream.shouldDiscardUnknownFields()' (com.google.protobuf.GeneratedMessageV3 is in unnamed module of loader java.net.URLClassLoader @319dead1; com.google.protobuf.CodedInputStream is in unnamed module of loader 'app')
        at com.google.protobuf.GeneratedMessageV3.parseUnknownField(GeneratedMessageV3.java:317)
        at com.android.server.adb.protos.AppProcessesProto$ProcessEntry.<init>(AppProcessesProto.java:119)
        at com.android.server.adb.protos.AppProcessesProto$ProcessEntry.<init>(AppProcessesProto.java:54)
        at com.android.server.adb.protos.AppProcessesProto$ProcessEntry$1.parsePartialFrom(AppProcessesProto.java:778)
        at com.android.server.adb.protos.AppProcessesProto$ProcessEntry$1.parsePartialFrom(AppProcessesProto.java:772)
        at com.google.protobuf.CodedInputStream$ArrayDecoder.readMessage(CodedInputStream.java:980)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses.<init>(AppProcessesProto.java:879)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses.<init>(AppProcessesProto.java:829)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses$1.parsePartialFrom(AppProcessesProto.java:1571)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses$1.parsePartialFrom(AppProcessesProto.java:1565)
        at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:111)
        at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:126)
        at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:20)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses.parseFrom(AppProcessesProto.java:1027)
        at com.android.ddmlib.internal.DeviceClientMonitorTask$TrackAppProcessor.processIncomingData(DeviceClientMonitorTask.java:505)
        at com.android.ddmlib.internal.DeviceClientMonitorTask.run(DeviceClientMonitorTask.java:252)
        at java.base/java.lang.Thread.run(Thread.java:842)

I have no idea what changed but this still occurs when I use a fresh flutter project.

Very strange but after some further inspection I get this error:
SEVERE: Fatal error while executing main with args: --proto_config=/Users/user/.android/utp/runnerConfig16394222982918146376.pb --proto_server_config=/Users/user/.android/utp/serverConfig12969538524026250445.pb
java.lang.IllegalAccessError: class com.google.protobuf.GeneratedMessageV3 tried to access method 'boolean com.google.protobuf.CodedInputStream.shouldDiscardUnknownFields()' (com.google.protobuf.GeneratedMessageV3 is in unnamed module of loader java.net.URLClassLoader @319dead1; com.google.protobuf.CodedInputStream is in unnamed module of loader 'app')
        at com.google.protobuf.GeneratedMessageV3.parseUnknownField(GeneratedMessageV3.java:317)
        at com.android.server.adb.protos.AppProcessesProto$ProcessEntry.<init>(AppProcessesProto.java:119)
        at com.android.server.adb.protos.AppProcessesProto$ProcessEntry.<init>(AppProcessesProto.java:54)
        at com.android.server.adb.protos.AppProcessesProto$ProcessEntry$1.parsePartialFrom(AppProcessesProto.java:778)
        at com.android.server.adb.protos.AppProcessesProto$ProcessEntry$1.parsePartialFrom(AppProcessesProto.java:772)
        at com.google.protobuf.CodedInputStream$ArrayDecoder.readMessage(CodedInputStream.java:980)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses.<init>(AppProcessesProto.java:879)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses.<init>(AppProcessesProto.java:829)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses$1.parsePartialFrom(AppProcessesProto.java:1571)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses$1.parsePartialFrom(AppProcessesProto.java:1565)
        at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:111)
        at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:126)
        at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:20)
        at com.android.server.adb.protos.AppProcessesProto$AppProcesses.parseFrom(AppProcessesProto.java:1027)
        at com.android.ddmlib.internal.DeviceClientMonitorTask$TrackAppProcessor.processIncomingData(DeviceClientMonitorTask.java:505)
        at com.android.ddmlib.internal.DeviceClientMonitorTask.run(DeviceClientMonitorTask.java:252)
        at java.base/java.lang.Thread.run(Thread.java:842)

I have no idea what changed but this still occurs when I use a fresh flutter project.

I had this exact problem in a pure Android project. I went into the ~/.gradle/caches/modules-2/files-2.1/com.google.protobuf/3.17.2, on mac, and delete the protobuf library. Then I commented out one dependency at a time and rebuilt the project. If the dependency didn't download then I found the dependency that was downloading the library. The library for me was classpath "com.android.tools.build:gradle". So I changed it's version until a different version of protobuf was downloaded and my build started working properly.


HDFS-16169.

Run TestBlockTokenWithDFSStriped#testEnd2End 30 times, the trunk version failed 5 times, the version with this patch failed 0 times.

For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
29m 34s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

-1 :x:
mvninstall
7m 27s
/branch-mvninstall-root.txt
root in trunk failed.

-1 :x:
compile
0m 29s
/branch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04.txt
hadoop-hdfs in trunk failed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04.

+1 :green_heart:
compile
1m 57s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m  2s

trunk passed

+1 :green_heart:
mvnsite
1m 35s

trunk passed

+1 :green_heart:
javadoc
1m  5s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 34s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 38s

trunk passed

+1 :green_heart:
shadedclient
29m 25s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m 14s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
compile
0m  9s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04.txt
hadoop-hdfs in the patch failed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04.

-1 :x:
javac
0m  9s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04.txt
hadoop-hdfs in the patch failed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04.

-1 :x:
compile
0m 23s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-hdfs in the patch failed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.

-1 :x:
javac
0m 23s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-hdfs in the patch failed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 21s
/buildtool-patch-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
The patch fails to run checkstyle in hadoop-hdfs

-1 :x:
mvnsite
0m 23s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

+1 :green_heart:
javadoc
0m 58s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 39s

the patch passed

+1 :green_heart:
shadedclient
25m 12s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
376m 30s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 45s

The patch does not generate ASF License warnings.

484m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3850/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3850

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 47b4c2e7b8f1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5b55e1f2f7be93e2647b784f0febff10d8b74164

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3850/1/testReport/

Max. process+thread count
2771 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3850/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  7s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 26s

trunk passed

+1 :green_heart:
compile
1m 25s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
1m 20s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m  2s

trunk passed

+1 :green_heart:
mvnsite
1m 29s

trunk passed

+1 :green_heart:
javadoc
1m  3s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 29s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 21s

trunk passed

+1 :green_heart:
shadedclient
22m 28s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 17s

the patch passed

+1 :green_heart:
compile
1m 24s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
1m 24s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 14s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 50s

the patch passed

+1 :green_heart:
mvnsite
1m 15s

the patch passed

+1 :green_heart:
javadoc
0m 51s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 25s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
3m 12s

the patch passed

+1 :green_heart:
shadedclient
28m 55s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
423m 19s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 48s

The patch does not generate ASF License warnings.

529m 23s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDecommissionWithStriped

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3850/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3850

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 87a8f358e072 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5b55e1f2f7be93e2647b784f0febff10d8b74164

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3850/2/testReport/

Max. process+thread count
2711 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3850/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Good catch!
@secfree Thanks for your contribution.


735 | Asteroid Collision | Python

Asteroid Collision -
What will change -
Type of Issue -

[x] Adding New Code

Programming Language

[x] Python

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

please assign this to me

please assign this to me...


Implement crash handling for Android

Implement AppWillTerminateWithError message sending in detox/android (implemented only on iOS).
This way (1) or another, improve quality of logs to help users understand what's going on in issues like these:

https://github.com/wix/detox/issues/395
https://github.com/wix/detox/issues/796
https://github.com/wix/detox/issues/799 (although, it might be not related)

This has been implemented by @d4vidi


Split KeyPress into separate Key and Modifier types.

Also refactor the escape seq. parser to be data-driven, making it easy to add support for these.
Fixes #318 , maybe some others. Big breaking change, but I tried to make the changes not as painful as they naively would be.
I need to test more, it's late, no rush on this review (It's big, but most of the parts were for updating code with the changes), it just bugged me is all.

I've tested this on various terminals and it seems to work well.

Thanks for all you do.
I just need some time to review all these changes...

No worries. The majority of it was done via find and replace FWIW, since it was basically a big rename of a lot of stuff.

Conflicts resolved in https://github.com/thomcc/rustyline/pull/1

Sorry for vanishing here, and thanks for taking over on the PR. I think there are a few sequences still missing from this (aside from ESC ESC, which is added by #517), but at some point I'll try to look into it, and if so, file a bug about them concretely.


Group Members Page Error

Error on accessing group's members page.
Happens on GCcollab Jobs Marketplace and The Policy Community so may be from the number of members they have.
Does not happen on Canada - Indigenous Relations: which is the 3rd largest.
Does happen on GCcollab Group Owners' and Operators' Corner the 4th largest.
Does not happen on Canada Beyond 150 the 5th largest.
Does not happen on The Future of Government the 6th largest.
Does happen on GCcollab Café the 7th largest.
Does happen on Intelli: The Latest on Public Sector Innovation the 8th largest.
Does not happen on Social Innovation the 9th largest.
Does happen to Talent Cloud the 10th largest.
Uncaught TypeError: Cannot use 'in' operator to search for '47' in Group was not found. Please try a different GUID

Current fix testing:
moving if (!elgg_is_logged_in()) { 		login($user_entity); 	}
to before the get_entity will make it work. This change might have to go for all the api functions.

Yes I think you moved that line of code above in a different API call, correct? If that's the fix, then we should do for all API calls.


Get us from F to a better grade: https://observatory.mozilla.org/analyze/start.microprofile.io

https://observatory.mozilla.org/analyze/start.microprofile.io

This is now solved: https://observatory.mozilla.org/analyze/starter.karms.biz

Grade is B.  With Grade A+ PrimeFaces are broken as it relies on inlining JS...   I guess B is O.K.

Demo: https://starter.karms.biz/
PR coming soon


C# strings with unicode escapes can be incorrectly translated to minified javascript

While you have really done an awesome work, fixing all my issues in the 17.8 release, a tiny problem still persists:
The encoding problem encountered in  #3902  is still present when generating the minified javascript output. There the unicode escapes are again replaced by single characters, which can not be handled by javascript correctly.

Yes, there is an issue. I don't think it's being caused by Bridge, but it's likely the minification tool we're using. We will have to investigate.

A fix for this issue has been created and we will include the fix in the next Bridge release.

The fix looks good and should make it to the next release (see assigned milestone).