Xcode 14 build failed with manual code sign and app resource bundles #11402

blastmann · 2022-06-08T02:09:05Z

I've read and understood the CONTRIBUTING guidelines and have done my best effort to follow.

Report

What did you do?

Integrate a pod with resource bundle.
Set app code sign style to Manual.
Build app with Xcode 14 beta.
It should failed with errors like below:

What did you expect to happen?

It should build success.

What happened instead?

Build failed.

CocoaPods Environment

Stack

   CocoaPods : 1.11.2
        Ruby : ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-darwin20]
    RubyGems : 3.1.4
        Host : macOS 12.4 (21F79)
       Xcode : 13.4 (13F17a)
         Git : git version 2.29.2
Ruby lib dir : /Users/eddiechan/.rbenv/versions/2.7.2/lib
Repositories : 
               trunk - CDN - https://cdn.cocoapods.org/

Installation Source

Executable Path: /Users/eddiechan/.rbenv/versions/2.7.2/bin/pod

Plugins

cocoapods-check                       : 1.1.0
cocoapods-deintegrate                 : 1.0.5
cocoapods-disable-podfile-validations : 0.1.1
cocoapods-generate                    : 2.2.2
cocoapods-open                        : 0.0.8
cocoapods-plugins                     : 1.0.0
cocoapods-search                      : 1.0.1
cocoapods-trunk                       : 1.6.0
cocoapods-try                         : 1.2.0

Project that demonstrates the issue

Xcode14ResBundle.zip

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

linconz · 2022-06-08T07:54:05Z

same issue, but you can use XCConfig to resolve like this:
First, find your Team ID in Apple Developer Membership.
Second, change your Podfile:

post_install do |installer|
  installer.generated_projects.each do |project|
    project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings["DEVELOPMENT_TEAM"] = " Your Team ID  "
         end
    end
  end
end

blastmann · 2022-06-09T06:13:00Z

@linconz Yes, I solve this issue by using post_install script too.

Buju77 · 2022-06-15T19:13:01Z

just out of curiosity, will this be fixed in Cocoapods in the end or is this just some Xcode 14 Beta 1 bug and we are hoping Apple will fix it in future betas and the bug will magically go away?

cdoky · 2022-06-23T01:35:45Z

The same problem.

cdoky · 2022-06-23T06:30:14Z

The Xcode14.0Beta2 fixed the problem.

dmcgloin · 2022-06-23T07:18:59Z

Xcode 14 Beta 2 actually resolves problem for me

Buju77 · 2022-06-23T11:16:03Z

Just tried Xcode 14.0 beta 2 (14A5229c) and still the same issue:

error: Cannot code sign because the target does not have an Info.plist file and one is not being generated automatically. Apply an Info.plist file to the target using the INFOPLIST_FILE build setting or generate one automatically by setting the GENERATE_INFOPLIST_FILE build setting to YES (recommended). (in target 'App' from project 'App')

evandorn · 2022-06-23T16:32:56Z

Fwiw this was not fixed for my project in Xcode 14 beta 2 either, the same issue persists.

damonxiao154 · 2022-06-29T08:07:30Z

same issue in Xcode 14.0 beta 2

rubencalde · 2022-06-30T16:19:50Z

After getting the same issue mentioned above, with RealmSwift 10.28.1:
error: Cannot code sign because the target does not have an Info.plist file and one is not being generated automatically. Apply an Info.plist file to the target using the INFOPLIST_FILE build setting or generate one automatically by setting the GENERATE_INFOPLIST_FILE build setting to YES (recommended). (in target 'App' from project 'App') ** BUILD FAILED **
We were able to fix this, by updating to the latest version of CocoaPods, 1.11.3 with version 1.22.0 of the xcodeproj gem. In this way it has been possible to validate the RealmSwift podspec.

Rubén

1677 · 2022-07-04T08:54:57Z

I wrote a CocoaPods plugin to solve this problem, everyone is welcome to use cocoapods-pod-sign

dyegos · 2022-07-18T11:55:42Z

I am still having issues with it using Xcode 14 beta 3. Is there going to be any fix from Cocoapods or are we waiting for Xcode to fix itself?

@1677 the plugin is awesome. However, it's not working on Xcode beta 3 :/
This application or a bundle it contains has the same bundle identifier as this application or another bundle that it contains. Bundle identifiers must be unique.

li6185377 · 2022-07-19T08:46:29Z

same issue, but you can use XCConfig to resolve like this: First, find your Team ID in Apple Developer Membership. Second, change your Podfile:
post_install do |installer|
  installer.generated_projects.each do |project|
    project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings["DEVELOPMENT_TEAM"] = " Your Team ID  "
         end
    end
  end
end

Automatically get main project Team ID

post_install do |installer|
    # Get main project development team id
    dev_team = ""
    project = installer.aggregate_targets[0].user_project
    project.targets.each do |target|
        target.build_configurations.each do |config|
            if dev_team.empty? and !config.build_settings['DEVELOPMENT_TEAM'].nil?
                dev_team = config.build_settings['DEVELOPMENT_TEAM']
            end
        end
    end
    
    # Fix bundle targets' 'Signing Certificate' to 'Sign to Run Locally'
    installer.pods_project.targets.each do |target|
        if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle"
            target.build_configurations.each do |config|
                config.build_settings['DEVELOPMENT_TEAM'] = dev_team
            end
        end
    end
end

blastmann · 2022-07-20T05:58:21Z

Actually, we can also set the CODE_SIGN_IDENTITY empty in order to avoid this issue, that's much easier. Like this:

    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['CODE_SIGN_IDENTITY'] = ''
        end
    end

knox · 2022-07-28T14:31:56Z

Actually, we can also set the CODE_SIGN_IDENTITY empty

Doesn't work for me when building for a device

doge1024 · 2022-08-01T16:55:43Z

Fix Xcode14 bundle need sign

post_install do |installer|
  installer.pods_project.targets.each do |target|
    if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle"
      target.build_configurations.each do |config|
          config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
      end
    end
  end
end

fabiendem · 2022-09-08T16:48:25Z

Hey, I can't find any good documentation around CODE_SIGNING_ALLOWED.
But CODE_SIGNING sounds important so I am a bit reluctant to drop that in our config without knowing what it's doing.
Could one of you clarify this please?

kconner · 2022-09-12T21:49:15Z

Issue is still present in CocoaPods 1.11.3 and GM release Xcode 14.0 (14A309). Applying one of these post-install measures would let me begin using Xcode 14 for now, but I'd like to do without a workaround.

CocoaPods/CocoaPods#11402 (comment)

anmolghosh · 2023-02-22T20:37:55Z

@dnkoutso When can we expect the release of 1.12.0? If the 1.12.0 timeline is not near its end, can this be released as patch to 1.11 instead?

zoobibackups · 2023-03-08T11:11:36Z

Add this to pod file

 post_install do |installer|
    react_native_post_install(installer)
    
    
    #############
      installer.pods_project.targets.each do |target|
            
        ### Added for Maps
        if target.name == 'RCT-Folly'
          target.build_configurations.each do |config|
            config.build_settings['HEADER_SEARCH_PATHS'] = "$(inherited) ${PODS_ROOT}/fmt/include"
            config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
          end
        end
        #### Added For Maps Ended 

        if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle"
          target.build_configurations.each do |config|
              config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
              config.build_settings["DEVELOPMENT_TEAM"] = "G2BW7BNX6K" 
          end
        end
      end
    ############


    installer.pods_project.build_configurations.each do |config|
      config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
      config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
      config.build_settings["ONLY_ACTIVE_ARCH"] = "YES"
    end
    #__apply_Xcode_12_5_M1_post_install_workaround(installer)
  
  end
end

douglascarvalho · 2023-03-08T22:02:36Z

Updating Cocoapods to 1.12.0 fixed the error for me on Xcode 14.2. Thanks.

UberMC · 2023-03-16T03:53:08Z

Updating Cocoapods to 1.12.0 fixed the error for me on Xcode 14.2. Thanks.

Thanks this also fixed AccessibilityResources.bundle' does not contain a bundle executable.
Since setting generate_Info_plist on the pods caused that error.

plindsay · 2023-03-23T16:42:21Z

I'm running into these issues too with Xcode 14 but struggling to update Cocoapods within my project to 1.12.0

If I run gem install cocoapods it looks like it installs 1.12.0 but if I run pod --version inside my ios directory it still shows version 1.11.2

How can I update my project to use Cocoapods 1.12.0?

julestruong · 2023-03-23T19:10:32Z

I'm running into these issues too with Xcode 14 but struggling to update Cocoapods within my project to 1.12.0

If I run gem install cocoapods it looks like it installs 1.12.0 but if I run pod --version inside my ios directory it still shows version 1.11.2

How can I update my project to use Cocoapods 1.12.0?

in your gemfile, don't you have something like this ?

gem 'cocoapods', '1.11.2'

change it to 1.12.0 and rerun : gem install?

tomwanzek · 2023-03-23T20:07:54Z

So the good news is that Cocoapods 1.12.0 seems to have addressed the iOS build issues we saw in our CI/CD pipeline after trying to bump it to latest XCode and fastlane stable releases. So 🙇 for that 😄

@plindsay I had the same experience, unlike any of my previous cocoapods upgrades to my local dev environment, this one created all sorts of weird behaviors. It wasn't really updating the discovered version in the existing path. I could find the executable and ran it directly with --version. While it did show the correct version 1.12.0, somehow it was barking that all its plugins were missing.

I updated my PATH variable based on some more paths from gem environment, but the issue with the missing plug-ins persisted.

Oddly enough, in the project repo I needed it in, we also have a Gemfile for use with bundler. Essentially for the CI/CD pipeline. When I manually updated it and ran bundler install the Gemfile lock was correctly updated including the cocoapods plug-ins.

Running bundler exec pod install in the same folder (it also contains the projects Podfile) ran 1.12.0 without any plug-in missing warnings.

TBH, not sure what's up with that. It's never been an issue before.

plindsay · 2023-03-24T09:20:39Z

Thanks @julestruong & @tomwanzek - updated the Gemfile to read gem 'cocoapods', '1.12.0' then gem install cocoapods once again. All went well, then cd into ios/ and ran bundler install - see output below -

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Using rexml 3.2.5
Using CFPropertyList 3.0.6
Using concurrent-ruby 1.2.2
Using i18n 1.12.0
Using minitest 5.18.0
Using tzinfo 2.0.6
Using activesupport 7.0.4.3
Using public_suffix 4.0.7
Using addressable 2.8.1
Using httpclient 2.8.3
Using json 2.6.3
Using algoliasearch 1.27.5
Using atomos 0.1.3
Using bundler 2.1.4
Using claide 1.1.0
Using fuzzy_match 2.0.4
Using nap 1.1.0
Using netrc 0.11.0
Using ffi 1.15.5
Using ethon 0.16.0
Using typhoeus 1.4.0
Using cocoapods-core 1.12.0
Using cocoapods-deintegrate 1.0.5
Using cocoapods-downloader 1.6.3
Using cocoapods-plugins 1.0.0
Using cocoapods-search 1.0.1
Using cocoapods-trunk 1.6.0
Using cocoapods-try 1.2.0
Using colored2 3.1.2
Using escape 0.0.4
Using fourflusher 2.3.1
Using gh_inspector 1.1.3
Using molinillo 0.8.0
Using ruby-macho 2.5.1
Using nanaimo 0.3.0
Using xcodeproj 1.22.0
Using cocoapods 1.12.0
Bundle complete! 1 Gemfile dependency, 37 gems now installed.
Bundled gems are installed into ../vendor/bundle

Then ran bundler exec pod install which again ran without errors, however pod --version still shows 1.11.2 and Xcode archive builds still fail... Have I missed a step somewhere?...

julestruong · 2023-03-24T09:30:07Z

That's odd.
Mine shows 1.12 and archive build successfully :(
Maybe there is another issue

penghuili · 2023-03-24T10:56:07Z

It seems upgrading cocoapods to 1.12.0 fixes the problem for everyone, but my current situation is this:

before upgrading cocoapods, we can't even publish the build from our CI to TestFlight, we always get the ITMS-90129: The bundle uses a bundle name or display name that is already taken. error message.

then we upgraded cocoapds, we can now publish the build from CI to TestFlight, but we will immediately get an email from apple, with exactly the same error message ITMS-90129: The bundle uses a bundle name or display name that is already taken., and the build won't appear in TestFlight.

does anyone have the same problem? or anyone has any idea?
thx 🙏

adamdahan · 2023-03-24T14:25:02Z

1.12.0 does not fix the problem for everyone.

Harukisatoh · 2023-03-29T18:40:45Z

I'm currently using App Center as CI, and updating the Cocoapods to 1.12.0 has no effect for me. The post install workarounds also don't work. All these solutions works locally, but not on CI. Any new solutions?

nodrock · 2023-03-29T20:20:44Z

We use this workaround since day one of XCode 14 and it worked with older Cocoapods as well as 1.12.0. We add these lines on CI to all projects:

post_install do |installer|
    # Get main project development team id
    dev_team = ""
    project = installer.aggregate_targets[0].user_project
    project.targets.each do |target|
        target.build_configurations.each do |config|
            if dev_team.empty? and !config.build_settings['DEVELOPMENT_TEAM'].nil?
              dev_team = config.build_settings['DEVELOPMENT_TEAM']
            end
        end
    end

    # Fix bundle targets' 'Signing Certificate' to 'Sign to Run Locally'
    installer.pods_project.targets.each do |target|
        target_is_resource_bundle = target.respond_to?(:product_type) && target.product_type == 'com.apple.product-type.bundle'
      
        if target_is_resource_bundle
            target.build_configurations.each do |config|
                config.build_settings["DEVELOPMENT_TEAM"] = dev_team
            end
        end
    end
end

penghuili · 2023-03-30T07:46:09Z

It seems upgrading cocoapods to 1.12.0 fixes the problem for everyone, but my current situation is this:

before upgrading cocoapods, we can't even publish the build from our CI to TestFlight, we always get the ITMS-90129: The bundle uses a bundle name or display name that is already taken. error message.

then we upgraded cocoapds, we can now publish the build from CI to TestFlight, but we will immediately get an email from apple, with exactly the same error message ITMS-90129: The bundle uses a bundle name or display name that is already taken., and the build won't appear in TestFlight.

does anyone have the same problem? or anyone has any idea? thx 🙏

As a follow to this, we figured out the reason for ITMS-90129: The bundle uses a bundle name or display name that is already taken., it is indeed because we used the same bundle name.

For our app, we have each app for each env, like App for prod, App-DEV for dev, App-RC for rc.
And all 3 apps have the same CFBundleName in the info.plist file.
with Xcode 13, this is not a problem, but xcode14 complains with that error message.

so, we changed the Fastfile to update the CFBundleName based on env, and everything started working.

haniewais · 2023-04-18T22:33:58Z

If you have different signing certificates for different schemes and don't need the pods signed, you can leave the Team in Xcode to none with the Automatically manage signing checked by default.

Then add the following config.build_settings... lines to the post_install step in your Pod file, example:

post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|

            # disable code signing for pods
            config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
            config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
            config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
        end
    end
end

posted here also:
https://stackoverflow.com/questions/72561696/xcode-14-needs-selected-development-team-for-pod-bundles/76049506#76049506

Dat-Mobile · 2023-04-28T04:24:29Z

If you have different signing certificates for different schemes and don't need the pods signed, you can leave the Team in Xcode to none with the Automatically manage signing checked by default.

Then add the following config.build_settings... lines to the post_install step in your Pod file, example:
post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|

            # disable code signing for pods
            config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
            config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
            config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
        end
    end
end
posted here also: https://stackoverflow.com/questions/72561696/xcode-14-needs-selected-development-team-for-pod-bundles/76049506#76049506

Even cocoapods 1.12 doesn't work, but this fix works for me

Fix xcode 14 build with this script: CocoaPods/CocoaPods#11402 (comment)

… for pods (facebook#34826) Summary: This is inspired by the Expo workaround expo/expo@d970a9e to address an issue that cocoapods has with Xcode 14: CocoaPods/CocoaPods#11402 This wants to address this facebook#34673 in a way that we can also cherry-pick on the 0.70 branch. ## Changelog  [iOS] [Fixed] - add xcode 14 workaround (turn off signing resource bundles) for `React-Core` Pull Request resolved: facebook#34826 Test Plan: Tested locally by opening RNTester via Xcode 14.0.1, and targetting my iPhone as device. After applying the patch, the error for React Core AccessibilityResources disappears. Also, added ruby test for new patch. Reviewed By: hramos Differential Revision: D40063828 Pulled By: hramos fbshipit-source-id: e10d5b6a917a6a7cbacd14ecfdac55e60e46c6f8

Refs: CocoaPods/CocoaPods#11402 (comment)

…igning framework bundles and for future visionOS support (see CocoaPods/CocoaPods#11402 . Thanks AlamoFire )

paulb777 mentioned this issue Jun 23, 2022

FirebaseInAppMessaging code sign error on Xcode 14 firebase/firebase-ios-sdk#9886

Closed

akovalov mentioned this issue Jun 29, 2022

Error in Xcode 14 beta via Cocoapods pmusolino/Wormholy#117

Open

rubencalde mentioned this issue Jun 30, 2022

Xcode 14 beta fails when build a Realm v10.28.1 watchOS Target realm/realm-swift#7848

Closed

oristanovic mentioned this issue Jul 8, 2022

Signing issues with Xcode Beta for Airship library installed via CocoaPods urbanairship/ios-library#328

Closed

wooj-stripe mentioned this issue Aug 5, 2022

[BUG] Unable to build with Xcode 14 beta stripe/stripe-ios#1991

Closed

knox mentioned this issue Sep 8, 2022

[XCode 14 issue]: No signing certificate iOS Development found. needs selected Development Team for Pod Bundles actions/runner-images#6190

Closed

10 tasks

crazymanish mentioned this issue Sep 10, 2022

[XCode 14 issue]: No signing certificate iOS Development found. needs selected Development Team for Pod Bundles fastlane/fastlane#20626

Closed

alexander-kurilovich-gismart mentioned this issue Sep 12, 2022

Xcode 14 - After pod install, need to assign development team to each and every Pod target #11534

Closed

1 task

nicolasdevienne mentioned this issue Sep 13, 2022

Build failed with new version of Xcode 14.0 :( stripe/stripe-react-native#1127

Closed

pnthach95 mentioned this issue Sep 13, 2022

Unable to build with XCode 14.0 facebook/react-native#34673

Closed

uzuki-P mentioned this issue Sep 13, 2022

Signing errors on iOS pod bundle resources on Xcode 14 "Signing for "x" requires a development team." flutter/flutter#111475

Closed

tsapeta mentioned this issue Sep 13, 2022

[ios] Turn off signing resource bundles in Xcode 14 expo/expo#19095

Merged

acezard added a commit to cozy/cozy-flagship-app that referenced this issue Jan 24, 2023

fix: allow build to work on xcode14

18bc022

CocoaPods/CocoaPods#11402 (comment)

evil159 mentioned this issue Jan 30, 2023

Fix static linking cocoapods mapbox/mapbox-maps-ios#1888

Merged

flypaper0 mentioned this issue Feb 10, 2023

[Cocoapods] Replace json resource with code constant WalletConnect/WalletConnectSwiftV2#715

Closed

supun19 mentioned this issue Feb 19, 2023

[🐛] Bug Report Title - CHANGE ME invertase/react-native-firebase#6921

Closed

onevcat mentioned this issue Feb 24, 2023

[iOS] Signing for "LineSDKSwift-LineSDK" requires a development team line/flutter_line_sdk#69

Closed

alexsegura mentioned this issue Apr 3, 2023

Build with iOS 16 SDK coopcycle/coopcycle-app#1489

Closed

roman-aliyev mentioned this issue Apr 23, 2023

updated CocoaPods to fix the issue #11402. mastodon/mastodon-ios#1027

Closed

chwo mentioned this issue May 4, 2023

Reconfigure the project in order to rid of Resources bundle prebid/prebid-mobile-ios#795

Closed

polar133 pushed a commit to klarna/react-native-klarna-inapp-sdk that referenced this issue May 9, 2023

Update podfile for Xcode 14

9014327

Fix xcode 14 build with this script: CocoaPods/CocoaPods#11402 (comment)

Bibazavr added a commit to lad-tech/mobydick that referenced this issue Jul 17, 2023

build: workaround for xcode 14

ff9f77b

Refs: CocoaPods/CocoaPods#11402 (comment)

paulb777 mentioned this issue Jan 26, 2024

Warning - Signing requires a development team google/gtm-session-fetcher#375

Closed

Soap-141 mentioned this issue Apr 23, 2024

ci: Fix iOS nventive/FlutterApplicationTemplate#6

Merged

17 tasks

DaveWoodCom added a commit to DaveWoodCom/XCGLogger that referenced this issue May 5, 2024

chore: set minimum CocoaPods version to 1.13.0 to avoid issues with s…

0799459

…igning framework bundles and for future visionOS support (see CocoaPods/CocoaPods#11402 . Thanks AlamoFire )

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Xcode 14 build failed with manual code sign and app resource bundles #11402

Xcode 14 build failed with manual code sign and app resource bundles #11402

blastmann commented Jun 8, 2022 •

edited

Loading

linconz commented Jun 8, 2022

blastmann commented Jun 9, 2022 •

edited

Loading

Buju77 commented Jun 15, 2022

cdoky commented Jun 23, 2022

cdoky commented Jun 23, 2022 •

edited

Loading

dmcgloin commented Jun 23, 2022 •

edited

Loading

Buju77 commented Jun 23, 2022

evandorn commented Jun 23, 2022

damonxiao154 commented Jun 29, 2022

rubencalde commented Jun 30, 2022

1677 commented Jul 4, 2022

dyegos commented Jul 18, 2022 •

edited

Loading

li6185377 commented Jul 19, 2022

blastmann commented Jul 20, 2022

knox commented Jul 28, 2022 •

edited

Loading

doge1024 commented Aug 1, 2022 •

edited

Loading

fabiendem commented Sep 8, 2022

kconner commented Sep 12, 2022 •

edited

Loading

anmolghosh commented Feb 22, 2023

zoobibackups commented Mar 8, 2023

douglascarvalho commented Mar 8, 2023

UberMC commented Mar 16, 2023

plindsay commented Mar 23, 2023

julestruong commented Mar 23, 2023 •

edited

Loading

tomwanzek commented Mar 23, 2023

plindsay commented Mar 24, 2023

julestruong commented Mar 24, 2023

penghuili commented Mar 24, 2023

adamdahan commented Mar 24, 2023

Harukisatoh commented Mar 29, 2023

nodrock commented Mar 29, 2023

penghuili commented Mar 30, 2023

haniewais commented Apr 18, 2023 •

edited

Loading

Dat-Mobile commented Apr 28, 2023

Xcode 14 build failed with manual code sign and app resource bundles #11402

Xcode 14 build failed with manual code sign and app resource bundles #11402

Comments

blastmann commented Jun 8, 2022 • edited Loading

Report

What did you do?

What did you expect to happen?

What happened instead?

CocoaPods Environment

Stack

Installation Source

Plugins

Project that demonstrates the issue

linconz commented Jun 8, 2022

blastmann commented Jun 9, 2022 • edited Loading

Buju77 commented Jun 15, 2022

cdoky commented Jun 23, 2022

cdoky commented Jun 23, 2022 • edited Loading

dmcgloin commented Jun 23, 2022 • edited Loading

Buju77 commented Jun 23, 2022

evandorn commented Jun 23, 2022

damonxiao154 commented Jun 29, 2022

rubencalde commented Jun 30, 2022

1677 commented Jul 4, 2022

dyegos commented Jul 18, 2022 • edited Loading

li6185377 commented Jul 19, 2022

blastmann commented Jul 20, 2022

knox commented Jul 28, 2022 • edited Loading

doge1024 commented Aug 1, 2022 • edited Loading

fabiendem commented Sep 8, 2022

kconner commented Sep 12, 2022 • edited Loading

anmolghosh commented Feb 22, 2023

zoobibackups commented Mar 8, 2023

douglascarvalho commented Mar 8, 2023

UberMC commented Mar 16, 2023

plindsay commented Mar 23, 2023

julestruong commented Mar 23, 2023 • edited Loading

tomwanzek commented Mar 23, 2023

plindsay commented Mar 24, 2023

julestruong commented Mar 24, 2023

penghuili commented Mar 24, 2023

adamdahan commented Mar 24, 2023

Harukisatoh commented Mar 29, 2023

nodrock commented Mar 29, 2023

penghuili commented Mar 30, 2023

haniewais commented Apr 18, 2023 • edited Loading

Dat-Mobile commented Apr 28, 2023

blastmann commented Jun 8, 2022 •

edited

Loading

blastmann commented Jun 9, 2022 •

edited

Loading

cdoky commented Jun 23, 2022 •

edited

Loading

dmcgloin commented Jun 23, 2022 •

edited

Loading

dyegos commented Jul 18, 2022 •

edited

Loading

knox commented Jul 28, 2022 •

edited

Loading

doge1024 commented Aug 1, 2022 •

edited

Loading

kconner commented Sep 12, 2022 •

edited

Loading

julestruong commented Mar 23, 2023 •

edited

Loading

haniewais commented Apr 18, 2023 •

edited

Loading