testLocationServicesButtonWithNoLocation, XCTAssertTrue failed

testLocationServicesButtonWithNoLocation, com.mbta.tid.mbtaapp.staging crashed in +[FIRApp addAppToAppDictionary:]

testLocationServicesButtonWithNoLocation, com.mbta.tid.mbtaapp.staging crashed in +[FIRApp addAppToAppDictionary:]

testLocationServicesButtonWithNoLocation, com.mbta.tid.mbtaapp.staging crashed in +[FIRApp addAppToAppDictionary:]

testNoRecenterWithNoLocation, XCTAssertTrue failed

testNoRecenterWithNoLocation, com.mbta.tid.mbtaapp.staging crashed in +[FIRApp addAppToAppDictionary:]

testNoRecenterWithNoLocation, com.mbta.tid.mbtaapp.staging crashed in +[FIRApp addAppToAppDictionary:]

testNoRecenterWithNoLocation, com.mbta.tid.mbtaapp.staging crashed in +[FIRApp addAppToAppDictionary:]

testLaunchPerformance, com.mbta.tid.mbtaapp.staging crashed in +[FIRApp addAppToAppDictionary:]

testLaunchPerformance, com.mbta.tid.mbtaapp.staging crashed in +[FIRApp addAppToAppDictionary:]

Cache not found for keys: setup-java-Linux-x64-gradle-db545925ec2f82b16a27964668b1de04f21a87f70746fd766d0f272b63bf372e

Cache not found for keys: setup-java-Linux-x64-gradle-db545925ec2f82b16a27964668b1de04f21a87f70746fd766d0f272b63bf372e

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache not found for keys: setup-java-Linux-x64-gradle-db545925ec2f82b16a27964668b1de04f21a87f70746fd766d0f272b63bf372e

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache not found for keys: setup-java-Linux-x64-gradle-db545925ec2f82b16a27964668b1de04f21a87f70746fd766d0f272b63bf372e

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Cache not found for keys: setup-java-macOS-arm64-gradle-db545925ec2f82b16a27964668b1de04f21a87f70746fd766d0f272b63bf372e

Cache not found for keys: setup-ruby-bundler-cache-v6-macos-14-arm64-ruby-3.2.2-wd-/Users/runner/work/mobile_app/mobile_app-with--without--only--Gemfile.lock-fdc2827012b52d9f61f15f22ad58e21599104211b4c3a5d1956b93f0ca047da8, setup-ruby-bundler-cache-v6-macos-14-arm64-ruby-3.2.2-wd-/Users/runner/work/mobile_app/mobile_app-with--without--only--Gemfile.lock-

xcbeautify 2.17.0 is already installed and up-to-date. To reinstall 2.17.0, run: brew reinstall xcbeautify

Interop library /Users/runner/.gradle/caches/modules-2/files-2.1/io.sentry/sentry-kotlin-multiplatform-iossimulatorarm64/0.10.0/e3877d150d892b92c954f3b7c843a6228f2e90f6/sentry-kotlin-multiplatform-cinterop-Sentry can't be exported with -Xexport-library

Interop library /Users/runner/.gradle/caches/modules-2/files-2.1/io.sentry/sentry-kotlin-multiplatform-iossimulatorarm64/0.10.0/94db602c2bd59efc23f118c3b86da675acc9802b/sentry-kotlin-multiplatform-cinterop-Sentry.Internal can't be exported with -Xexport-library

'func shared.Scope.setContext(key: Swift.String, value: Any) -> Swift.Void' was renamed to 'func shared.Scope.setContext_(key: Swift.String, value: Any) -> Swift.Void' because of a name collision with an another declaration 'func shared.Scope.setContext(key: Swift.String, value: Any) -> Swift.Void'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'func shared.Scope.setContext(key: Swift.String, value: Any) -> Swift.Void' was renamed to 'func shared.Scope.setContext__(key: Swift.String, value: Any) -> Swift.Void' because of a name collision with an another declaration 'func shared.Scope.setContext(key: Swift.String, value: Any) -> Swift.Void'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var shared.Alert.description' was renamed to 'var shared.Alert.description_' because of a name collision with an another declaration 'func shared.BackendObject.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var shared.Ktor_httpHttpStatusCode.description' was renamed to 'var shared.Ktor_httpHttpStatusCode.description_' because of a name collision with an another declaration 'func shared.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var shared.ObjectCollectionBuilder.AlertBuilder.description' was renamed to 'var shared.ObjectCollectionBuilder.AlertBuilder.description_' because of a name collision with an another declaration 'func shared.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var shared.ObjectCollectionBuilder.StopBuilder.description' was renamed to 'var shared.ObjectCollectionBuilder.StopBuilder.description_' because of a name collision with an another declaration 'func shared.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var shared.Stop.description' was renamed to 'var shared.Stop.description_' because of a name collision with an another declaration 'func shared.BackendObject.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'func shared.ExpCompanion.in(keyword: shared.Exp, input: shared.Exp) -> shared.Exp' was renamed to 'func shared.ExpCompanion.in_(keyword: shared.Exp, input: shared.Exp) -> shared.Exp' because of a name collision with an another declaration 'func shared.ExpCompanion.in(keyword: shared.Exp, input: shared.Exp) -> shared.Exp'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.