SDK 49 - eas build ios failed on "run fastlane" #2109

johnfau · 2023-11-03T09:25:21Z

Build/Submit details page URL

https://expo.dev/accounts/johnfa/projects/carles-connect/builds/5f04dc92-7dbc-42c8-9f9f-bb1dac0c7b2c#run-fastlane

Summary

We started a new project with expo 49. It errors with the following message :

Build failed: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.

We don't see any errors in Xcode logs, I put the end of the log on the Error ouput below.

Another project on the same expo account, same computer, same ios credentials (except for provisionning) on expo 47 still builds correctly.

We don't have any Mac device to test a local build which make the issue extra-difficult to understand. We tried suggestion from #2024 and expo/expo#25105 but the error remained.

Managed or bare?

managed

Environment

expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.19045
Binaries:
Node: 18.6.0 - C:\Program Files\nodejs\node.EXE
npm: 8.13.2 - C:\Program Files\nodejs\npm.CMD
npmPackages:
@expo/webpack-config: ^19.0.0 => 19.0.0
expo: ~49.0.11 => 49.0.16
react: 18.2.0 => 18.2.0
react-native: 0.72.6 => 0.72.6
react-native-web: ~0.19.6 => 0.19.9
Expo Workflow: managed

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK

Didn't find any issues with the project!

Error output

Build failed: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.

    /usr/bin/codesign --force --sign REDACTED --entitlements /Users/expo/Library/Developer/Xcode/DerivedData/AppNameRedacted-REDACTED/Build/Intermediates.noindex/ArchiveIntermediates/AppNameRedacted/IntermediateBuildFilesPath/AppNameRedacted.build/Release-iphoneos/AppNameRedacted.build/AppNameRedacted.app.xcent --generate-entitlement-der /Users/expo/Library/Developer/Xcode/DerivedData/AppNameRedacted-REDACTED/Build/Intermediates.noindex/ArchiveIntermediates/AppNameRedacted/InstallationBuildProductsLocation/Applications/AppNameRedacted.app

RegisterExecutionPolicyException /Users/expo/Library/Developer/Xcode/DerivedData/AppNameRedacted-REDACTED/Build/Intermediates.noindex/ArchiveIntermediates/AppNameRedacted/InstallationBuildProductsLocation/Applications/AppNameRedacted.app (in target 'AppNameRedacted' from project 'AppNameRedacted')

    cd /Users/expo/workingdir/build/ios

    builtin-RegisterExecutionPolicyException /Users/expo/Library/Developer/Xcode/DerivedData/AppNameRedacted-REDACTED/Build/Intermediates.noindex/ArchiveIntermediates/AppNameRedacted/InstallationBuildProductsLocation/Applications/AppNameRedacted.app

Validate /Users/expo/Library/Developer/Xcode/DerivedData/AppNameRedacted-REDACTED/Build/Intermediates.noindex/ArchiveIntermediates/AppNameRedacted/InstallationBuildProductsLocation/Applications/AppNameRedacted.app (in target 'AppNameRedacted' from project 'AppNameRedacted')

    cd /Users/expo/workingdir/build/ios

    builtin-validationUtility /Users/expo/Library/Developer/Xcode/DerivedData/AppNameRedacted-REDACTED/Build/Intermediates.noindex/ArchiveIntermediates/AppNameRedacted/InstallationBuildProductsLocation/Applications/AppNameRedacted.app

Touch /Users/expo/Library/Developer/Xcode/DerivedData/AppNameRedacted-REDACTED/Build/Intermediates.noindex/ArchiveIntermediates/AppNameRedacted/InstallationBuildProductsLocation/Applications/AppNameRedacted.app (in target 'AppNameRedacted' from project 'AppNameRedacted')

    cd /Users/expo/workingdir/build/ios

    /usr/bin/touch -c /Users/expo/Library/Developer/Xcode/DerivedData/AppNameRedacted-REDACTED/Build/Intermediates.noindex/ArchiveIntermediates/AppNameRedacted/InstallationBuildProductsLocation/Applications/AppNameRedacted.app

Reproducible demo or steps to reproduce from a blank project

run eas build --platform ios from my expo account on a project with expo ~49.0.11

{
  "name": "app",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {
    "start": "expo start",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web"
  },
  "dependencies": {
    "@expo/webpack-config": "^19.0.0",
    "@react-native-async-storage/async-storage": "1.18.2",
    "axios": "^1.5.0",
    "expo": "~49.0.11",
    "expo-asset": "~8.10.1",
    "expo-constants": "~14.4.2",
    "expo-dev-client": "~2.4.11",
    "expo-file-system": "~15.4.4",
    "expo-font": "~11.4.0",
    "expo-intent-launcher": "~10.7.0",
    "expo-linear-gradient": "~12.3.0",
    "expo-linking": "~5.0.2",
    "expo-media-library": "~15.4.1",
    "expo-router": "^2.0.0",
    "expo-splash-screen": "~0.20.5",
    "expo-status-bar": "~1.6.0",
    "nativewind": "^2.0.11",
    "react": "18.2.0",
    "react-native": "0.72.6",
    "react-native-gesture-handler": "~2.12.0",
    "react-native-safe-area-context": "4.6.3",
    "react-native-screens": "~3.22.0",
    "react-native-svg": "13.9.0",
    "react-native-toast-message": "^2.1.7",
    "react-native-view-shot": "3.7.0",
    "react-native-web": "~0.19.6",
    "react-native-webview": "13.2.2",
    "expo-network": "~5.4.0"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@expo/vector-icons": "^13.0.0",
    "@uidotdev/usehooks": "^2.4.0",
    "js-base64": "^3.7.5",
    "lodash-es": "^4.17.21",
    "react-native-anchor-point": "^1.0.6",
    "react-native-element-dropdown": "^2.10.0",
    "react-native-linear-gradient": "^2.8.3",
    "react-native-outside-press": "^1.2.1",
    "react-native-snap-carousel": "^4.0.0-beta.6",
    "tailwindcss": "3.3.2"
  },
  "private": true
}

The text was updated successfully, but these errors were encountered:

iam-rohid · 2023-11-05T06:03:30Z

I'm also having the same issue

jake-stewart · 2023-11-06T04:36:32Z

I am facing the same issue

LaKrue · 2023-11-08T14:50:15Z

Not sure if it's related, but I had errors like that. Building without associatedDomains in app.json for iOS linking worked, but failed with it. As hinted in #1687 I ran my build command without --non-interactive and it worked. Should note that I also deleted kind of everything app related from my apple dev account to have it regenerated.

jwNorwood · 2023-11-08T15:37:55Z

I am running into the same issue, works on Expo 47, iOS build fails on 48/49 but android build works.

johnfau · 2023-11-08T23:51:00Z

I don't use associatedDomains.
I always run build without --non-interactive.
Dev builds are working fine for both android and ios. I can use the app on the ad-hoc provisioned iphone device. Only the production build for iOS is failing eas build --platform ios

› Generating debug CConnect » CConnect .app.dSYM

› Executing CConnect » Bundle React Native code and images

    Bundler cache is empty, rebuilding (this may take a minute)

› Executing CConnect » [CP] Copy Pods Resources

› Executing CConnect » [CP] Embed Pods Frameworks

› Signing   CConnect » CConnect .app

› Creating  CConnect » CConnect .app

    Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' 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 'EXConstants' from project 'Pods')

▸ ** ARCHIVE FAILED **

2023-11-08 02:06:10.948 xcodebuild[4670:13722] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)

** ARCHIVE FAILED **

Exit status: 65

sascha93 · 2023-11-11T06:41:45Z

I am running into the same issue, works on Expo 47, iOS build fails on 48/49 but android build works.

same here

szdziedzic · 2023-11-14T11:25:49Z

Hi,

This issue seems super weird and I feel like it can be related to some issues with your credentials. Did you verify that all of your certificates are valid on the Apple Developer Portal?

johnfau · 2023-11-14T11:55:37Z

Hi,

This issue seems super weird and I feel like it can be related to some issues with your credentials. Did you verify that all of your certificates are valid on the Apple Developer Portal?

Yes, I even recreated fresh certificates, profiles and identifiers as suggested in #2024 . I didnt delete them as we are using them on another project but if it is necessary we can try

szdziedzic · 2023-11-14T12:51:14Z

Can you try to run a simulator build? If the issue itself is related to credentials, which sim builds don't use, it should work well.

johnfau · 2023-11-15T01:00:11Z

Can you try to run a simulator build? If the issue itself is related to credentials, which sim builds don't use, it should work well.

Yes simulator build is working well.

I deleted all certificates and profiles from apple developer account. I couldn't delete Identifiers from apple developer account as I get a message "The App ID 'XXX' appears to be in use by the App Store".

I ran again eas build ios , new certificate and profiles have been created but the build failed with the same error.

szdziedzic · 2023-11-15T10:04:40Z

Are you using local credentials or credentials managed by EAS?

johnfau · 2023-11-15T13:10:03Z

We are using the default method which I think is managed by EAS. I can see all my certificates and keys on my expo.dev account.

BogdanJWK · 2023-11-28T08:54:43Z

Any update? I'm going through the same thing, no solution so far.
Edit: In the meantime I decided to use eas remote build which works fine, but would still like to build locally.

Christian-Mugumwa · 2023-11-28T10:21:04Z

Going through the same issue here too

andrewminton · 2023-11-28T20:18:14Z

Having same issue on SDK 46,47,49. Can't deploy at all here. Frustrating error that wasn't here 2 months ago. Any updates/workarounds?

humbroll · 2023-12-05T03:13:50Z

Got the same issue. Has anyone figured out solution ?

Christian-Mugumwa · 2023-12-05T03:25:50Z

@humbroll @andrewminton So I fixed this by going into app.json and changing "bundleIdentifier" to something unique. Initially just changed it to a random number (try make it as random as possible). Then later changed it to com.myname.app and it worked.

I think the issue resides in that it has to be unique for some reason. I hope this works for you.

johnfau · 2023-12-05T04:03:11Z

@humbroll @andrewminton So I fixed this by going into app.json and changing "bundleIdentifier" to something unique. Initially just changed it to a random number (try make it as random as possible). Then later changed it to com.myname.app and it worked.

I think the issue resides in that it has to be unique for some reason. I hope this works for you.

I did it, generated new distribution certificate and provisionning profile but still got the exact same error.

dattx1 · 2023-12-13T23:56:22Z

--local --non-interactive it's worked for me, thank @LaKrue saved my day

johnfau · 2023-12-14T00:52:14Z

--non-intereactive doesnt help.

We finally got a Mac (the very thing we wanted to avoid using eas...) and tried to build on it we the same result. Here is the full log of a failed build from project creation to error. We used the basic project template, expo project creation and new certificate and profile creation. It is basically :

npx create-expo-app frbeprojo001
cd frbeprojo001
npm run ios
> iOs bundling complete and project opens correctly in iPhone emulator
npx eas-cli@latest build:configure
npx eas-cli@latest build --platform ios --local
> RUN_FASTLANE error, Archive failed

eas-cli-build-error.pdf

I have no idea what other test I could do from there. I guess the error in related to something in our apple developer account but buying a new account for test purpose seems a bit much.

dattx1 · 2023-12-14T01:03:46Z

eas build -p ios -e sit --clear-cache --local --non-interactive
This is my build command, after add the --non-interactive agr i can build normaly

johnfau · 2023-12-14T02:13:00Z

No change

BogdanJWK · 2023-12-14T09:27:50Z

I eventually switched to build my app from Xcode. I had some credentials/provision issues and recreated all of them in order to make it work. EAS fails with a different error now, regarding my ad-hoc credentials, but for the moment I consider building exclusively from xcode.

ahmed-khlifi · 2023-12-14T16:54:53Z

Any updates about this issue ? ( Am on SDK 48 )

dattx1 · 2023-12-19T13:53:33Z

Clean Xcode project build (production => clean build folder)

Close Xcode

Open terminal

Run cd ~/Library/Developer/Xcode/DerivedData && open .

Delete all item in folder

Open terminal and cd to project

yarn && npx pod-install ios

Open Xcode

Wait to Xcode index project

After Xcode finish index project => Start build (command + B)

After build finish run eas build -p ios -e sit --clear-cache --local --non-interactive

Please wait the xcode finish all step

Just-Moh-it · 2023-12-30T05:04:05Z

Having the same issue... tried everything in the thread but still failing at fastlane. If it helps, cloud builds and simulator builds work.

johnfau · 2024-01-11T08:53:41Z

I was able to publish on Mac using Xcode and @dattx1 steps. Build on eas still errors even when I try to use the provisioning and certificate created by Xcode.
Having to use a MAC to publish is a big step back for us :(

weetos · 2024-01-15T08:25:23Z

Hello friends,
I also was struggling with this issue past days! Drived me crazy!
Because at best the xcode build logs were misleading me... and very much like all of you Expo x Fastlane was throwing nothing more than error 65.
So what I did is to clean all my project and rebuild it, step by step, to find what was breaking my bundling.
Here are my findings:

I am using @react-navigation/stack for my navigation between screens. For whatever reason the following options {{ headerShown: false, presentation: 'card', animationTypeForReplace: 'pop', animation: 'slide_from_right' }}
caused the bundling to fail on iOS. I figured that it wasn't too happy with the props animation. So I removed it.
In my StyleSheet I had a duplicated key.

Now it's bundling like a charm ;)

But seriously the error log management is horrible!

I hope it will help some of you out there...

andreibardas · 2024-01-24T15:10:05Z

tried multiple possible solutions, nothing worked so far

gustavo-fior · 2024-01-24T23:11:41Z

--local --non-interactive it's worked for me, thank @LaKrue saved my day

THIS MAN IS A GOD AMONG HUMANS.

3 days of this bullshit, thanks a lot man

murat0 · 2024-02-01T09:53:21Z

Clearing the derived data and letting the script to build it again is precisely what worked for us;

rm -rf ~/Library/Developer/Xcode/DerivedData/*

CapleaIonut-Alexandru · 2024-02-05T15:58:41Z

I have the same issue, nothing works from here

andreibardas · 2024-02-21T00:10:13Z

Tried everything here but nothing works. Anyone found a solution for this? I am thinking about starting a new project with the latest expo version and copy pasting every component manually and running builds until I see something that breaks the build.

VadymBezsmertnyi · 2024-02-26T07:11:50Z

@andreibardas
I am facing the same issue

shahidul5 · 2024-02-28T14:46:36Z

@andreibardas any solution? I'm facing the same issue.

VadymBezsmertnyi · 2024-02-29T05:02:33Z

@dev-shahidul
It helped me:

npx react-native-clean-project
npx expo-doctor
npx expo install --fix
npx expo prebuild --clean
Opened Xcode and waited until everything checked out and the first time without warnings.
ran the command from package.json: "ios": "expo run:ios",

EmanuelOcampo · 2024-02-29T06:00:58Z

@VadymBezsmertnyi
it works for me thanks

debashreecbnits · 2024-03-12T19:56:23Z

@VadymBezsmertnyi you are a savior..thanks

mikeRChambers610 · 2024-05-17T15:50:54Z

I am getting this issues as well and so far all of the above comment suggestions have not worked for me. The build was working fine on SDK 49 and now not working for me anymore once upgrading to SDK 51. My dev build was perfectly fine in the expo go app.

lalobecerra7 · 2024-05-18T16:27:19Z

@dev-shahidul It helped me:

npx react-native-clean-project

npx expo-doctor

npx expo install --fix

npx expo prebuild --clean
Opened Xcode and waited until everything checked out and the first time without warnings.

ran the command from package.json: "ios": "expo run:ios",

This worked for me, thanks.

nickmaio · 2024-05-29T21:03:23Z

I am getting this issues as well and so far all of the above comment suggestions have not worked for me. The build was working fine on SDK 49 and now not working for me anymore once upgrading to SDK 51. My dev build was perfectly fine in the expo go app.

Same issue after upgrading to SDK 51.

landorid · 2024-06-03T15:09:05Z

Set export EAS_LOCAL_BUILD_SKIP_CLEANUP=1 so you can actually read your logs. My issue was with the provision cert, i deleted all the related certificates from the keychain and my build was successful.

johnfau · 2024-06-06T03:17:29Z

None of previous answers applied to my issue. I updated to 50 and 51 with same result. The absence of meaningful log on the run fastlane step is the real problem here, there are countless issues which can lead to the "archive failed" message and nothing of importance in the Xcode logs.

I finally figured out that my problem was a duplicate key in a js object. It seems like the fastlane build for iOS fail if one object has a duplicate key which make me think it might be a lint error during build.

very simple steps to reproduce:

npx create-expo-app .

edit _layout.tsx with

const bug = {
    error: "",
    test: 3,
    error: 123,
};

npm install
npx expo start

==> the app runs fine on android and iOS

npx eas-cli@latest build:configure
npx eas-cli@latest build --platform ios

==> build fail
remove the bug object from _layout.tsx

npx eas-cli@latest build --platform ios

==> build success

I don't think it is normal to fail a build for a duplicate key, especially without error message. My initial project is not on typescript, only the ESLint "no-dupe-keys" rule raise a warning.

nickmaio · 2024-06-06T05:02:39Z

None of previous answers applied to my issue. I updated to 50 and 51 with same result. The absence of meaningful log on the run fastlane step is the real problem here, there are countless issues which can lead to the "archive failed" message and nothing of importance in the Xcode logs.

I finally figured out that my problem was a duplicate key in a js object. It seems like the fastlane build for iOS fail if one object has a duplicate key which make me think it might be a lint error during build.

very simple steps to reproduce:
npx create-expo-app .
edit _layout.tsx with
const bug = {
    error: "",
    test: 3,
    error: 123,
};
npm install
npx expo start 
==> the app runs fine on android and iOS
npx eas-cli@latest build:configure
npx eas-cli@latest build --platform ios
==> build fail remove the bug object from _layout.tsx
npx eas-cli@latest build --platform ios
==> build success

I don't think it is normal to fail a build for a duplicate key, especially without error message. My initial project is not on typescript, only the ESLint "no-dupe-keys" rule raise a warning.

Same here, took a few days and 50+ build attempts to locate a breaking object { error: false, error: false } in a project with about a 250K+ lines of code. Horrible experience indeed...

Ebenezerayola · 2024-06-20T23:32:46Z

I am getting this issues as well and so far all of the above comment suggestions have not worked for me. The build was working fine on SDK 49 and now not working for me anymore once upgrading to SDK 51. My dev build was perfectly fine in the expo go app.

Same issue after upgrading to SDK 51.

Hello, were you able to resolve it?

kalashovkerim · 2024-06-24T20:37:02Z

expo v50, I fix it!
just deleted @sentry/react-native

Ebenezerayola · 2024-06-24T21:28:06Z

expo v50, I fix it! just deleted @sentry/react-native

I'm not I have this, where can I find it so I can also delete it?

kalashovkerim · 2024-06-24T21:31:50Z

expo v50, I fix it! just deleted @sentry/react-native

I'm not I have this, where can I find it so I can also delete it?

package.json
than delete sentry imports in all files where are you using it

Ebenezerayola · 2024-06-24T22:14:52Z

expo v50, I fix it! just deleted @sentry/react-native

I'm not I have this, where can I find it so I can also delete it?

package.json than delete sentry imports in all files where are you using it

I don't have sentry

kalashovkerim · 2024-06-24T22:18:49Z

oh, so just carefuly read log where maybe you will see ❌ emodji, and it will tell you what package is giving you error, in my case i saw that problem with sentry package

sousalucas · 2024-10-01T01:35:53Z

@dev-shahidul It helped me:

npx react-native-clean-project

npx expo-doctor

npx expo install --fix

npx expo prebuild --clean
Opened Xcode and waited until everything checked out and the first time without warnings.

ran the command from package.json: "ios": "expo run:ios",

work like a charm!

Nantris · 2024-10-17T00:18:56Z

Continuing to see this on SDK 51 with React Native 0.75.

gurbuzzomer · 2024-10-29T08:59:00Z

In my case, these were the things I had to do ;

1.Go to eas credentials and recreate your provisioning and distribution certificates
2. Go to App Store Connect to see whether there are any agreements that the Account Owner has to agree to
3. If there is a path in your app.js file that has not been gitignored, remove it from gitignore

Th1nhNg0 · 2024-10-30T02:50:46Z

Continuing to see this on SDK 51 with React Native 0.74.5

Nantris · 2024-10-30T03:02:49Z

FWIW our issue ended up being one of our other native dependencies silently causing the error. Remove them all and then add them back one by one to determine which is the cause.

Th1nhNg0 · 2024-10-30T03:51:12Z

For me i have to upgrade xcode to new ios version xD

johnfau added the needs review Issue is ready to be reviewed by a maintainer label Nov 3, 2023

szdziedzic added the eas build label Nov 14, 2023

yeoniii20 mentioned this issue Apr 10, 2024

build error SUNNY-PJ/Frontend#1

Closed

JeanBaptisteBolh mentioned this issue Sep 17, 2024

Error/warning on failing build: "Can't merge pod_target_xcconfig for pod targets" #2434

Open

SDK 49 - eas build ios failed on "run fastlane" #2109

SDK 49 - eas build ios failed on "run fastlane" #2109

Comments

johnfau commented Nov 3, 2023

Build/Submit details page URL

Summary

Managed or bare?

Environment

Error output

Reproducible demo or steps to reproduce from a blank project

iam-rohid commented Nov 5, 2023

jake-stewart commented Nov 6, 2023

LaKrue commented Nov 8, 2023

jwNorwood commented Nov 8, 2023

johnfau commented Nov 8, 2023

sascha93 commented Nov 11, 2023

szdziedzic commented Nov 14, 2023

johnfau commented Nov 14, 2023 • edited Loading

szdziedzic commented Nov 14, 2023

johnfau commented Nov 15, 2023

szdziedzic commented Nov 15, 2023

johnfau commented Nov 15, 2023

BogdanJWK commented Nov 28, 2023 • edited Loading

Christian-Mugumwa commented Nov 28, 2023

andrewminton commented Nov 28, 2023

humbroll commented Dec 5, 2023

Christian-Mugumwa commented Dec 5, 2023

johnfau commented Dec 5, 2023

dattx1 commented Dec 13, 2023 • edited Loading

johnfau commented Dec 14, 2023

dattx1 commented Dec 14, 2023

johnfau commented Dec 14, 2023

BogdanJWK commented Dec 14, 2023

ahmed-khlifi commented Dec 14, 2023 • edited Loading

dattx1 commented Dec 19, 2023

Just-Moh-it commented Dec 30, 2023

johnfau commented Jan 11, 2024

weetos commented Jan 15, 2024 • edited Loading

andreibardas commented Jan 24, 2024

gustavo-fior commented Jan 24, 2024

murat0 commented Feb 1, 2024

CapleaIonut-Alexandru commented Feb 5, 2024

andreibardas commented Feb 21, 2024

VadymBezsmertnyi commented Feb 26, 2024

shahidul5 commented Feb 28, 2024 • edited Loading

VadymBezsmertnyi commented Feb 29, 2024

EmanuelOcampo commented Feb 29, 2024

debashreecbnits commented Mar 12, 2024

mikeRChambers610 commented May 17, 2024

lalobecerra7 commented May 18, 2024

nickmaio commented May 29, 2024

landorid commented Jun 3, 2024 • edited Loading

johnfau commented Jun 6, 2024 • edited Loading

nickmaio commented Jun 6, 2024

Ebenezerayola commented Jun 20, 2024

kalashovkerim commented Jun 24, 2024

Ebenezerayola commented Jun 24, 2024

kalashovkerim commented Jun 24, 2024

Ebenezerayola commented Jun 24, 2024

kalashovkerim commented Jun 24, 2024

sousalucas commented Oct 1, 2024

Nantris commented Oct 17, 2024

gurbuzzomer commented Oct 29, 2024

Th1nhNg0 commented Oct 30, 2024

Nantris commented Oct 30, 2024

Th1nhNg0 commented Oct 30, 2024

johnfau commented Nov 14, 2023 •

edited

Loading

BogdanJWK commented Nov 28, 2023 •

edited

Loading

dattx1 commented Dec 13, 2023 •

edited

Loading

ahmed-khlifi commented Dec 14, 2023 •

edited

Loading

weetos commented Jan 15, 2024 •

edited

Loading

shahidul5 commented Feb 28, 2024 •

edited

Loading

landorid commented Jun 3, 2024 •

edited

Loading

johnfau commented Jun 6, 2024 •

edited

Loading