Could not find or use auto-linked library '..." #755

haveamission · 2020-05-24T21:05:17Z

🐛 Bug Report

Upon installing this library, and installing the pods, I try to run a build on the simulator. I get the following error (it was building properly before):

ld: warning: Could not find or use auto-linked library 'swiftCoreFoundation'
ld: warning: Could not find or use auto-linked library 'swiftCompatibility50'
ld: warning: Could not find or use auto-linked library 'swiftObjectiveC'
ld: warning: Could not find or use auto-linked library 'swiftFoundation'
ld: warning: Could not find or use auto-linked library 'swiftsimd'
ld: warning: Could not find or use auto-linked library 'swiftDarwin'
ld: warning: Could not find or use auto-linked library 'swiftUIKit'
ld: warning: Could not find or use auto-linked library 'swiftCore'
ld: warning: Could not find or use auto-linked library 'swiftQuartzCore'
ld: warning: Could not find or use auto-linked library 'swiftCoreGraphics'
ld: warning: Could not find or use auto-linked library 'swiftPhotos'
ld: warning: Could not find or use auto-linked library 'swiftSwiftOnoneSupport'
ld: warning: Could not find or use auto-linked library 'swiftCoreImage'
ld: warning: Could not find or use auto-linked library 'swiftCompatibilityDynamicReplacements'
ld: warning: Could not find or use auto-linked library 'swiftMetal'
ld: warning: Could not find or use auto-linked library 'swiftDispatch'
ld: warning: Could not find or use auto-linked library 'swiftAVFoundation'
ld: warning: Could not find or use auto-linked library 'swiftCoreMedia'
ld: warning: Could not find or use auto-linked library 'swiftCoreAudio'
ld: warning: Could not find or use auto-linked library 'swiftCoreMIDI'
ld: warning: Could not find or use auto-linked library 'swiftCoreLocation'
Undefined symbols for architecture x86_64:
  "protocol descriptor for Foundation.CustomNSError", referenced from:
      protocol conformance descriptor for __C_Synthesized.related decl 'e' for FBSDKLoginError : Foundation.CustomNSError in __C_Synthesized in libFBSDKLoginKit.a(LoginManager.o)
  "method descriptor for static Foundation.CustomNSError.errorDomain.getter : Swift.String", referenced from:
      protocol conformance descriptor for __C_Synthesized.related decl 'e' for FBSDKLoginError : Foundation.CustomNSError in __C_Synthesized in libFBSDKLoginKit.a(LoginManager.o)
  "method descriptor for Foundation.CustomNSError.errorUserInfo.getter : [Swift.String : Any]", referenced from:
      protocol conformance descriptor for __C_Synthesized.related decl 'e' for FBSDKLoginError : Foundation.CustomNSError in __C_Synthesized in libFBSDKLoginKit.a(LoginManager.o)
  "method descriptor for Foundation.CustomNSError.errorCode.getter : Swift.Int", referenced from:
      protocol conformance descriptor for __C_Synthesized.related decl 'e' for FBSDKLoginError : Foundation.CustomNSError in __C_Synthesized in libFBSDKLoginKit.a(LoginManager.o)
  "base conformance descriptor for Foundation.CustomNSError: Swift.Error", referenced from:
      protocol conformance descriptor for __C_Synthesized.related decl 'e' for FBSDKLoginError : Foundation.CustomNSError in __C_Synthesized in libFBSDKLoginKit.a(LoginManager.o)
  "protocol descriptor for Foundation._ErrorCodeProtocol", referenced from:

To Reproduce

Install library, install pods, try to build

Expected Behavior

Successful build

Environment

System:
OS: macOS 10.15.1
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 200.69 MB / 16.00 GB
Shell: 5.7.1 - /usr/local/bin/zsh
Binaries:
Node: 13.11.0 - /usr/local/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.13.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 25, 27, 28
Build Tools: 25.0.2, 26.0.2, 28.0.3
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5692245
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
npmPackages:
react: ^16.10.2 => 16.10.2
react-native: ^0.61.2 => 0.61.2
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
react-native: 0.60.5

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

AndrewJack · 2020-05-26T15:34:42Z

facebook-ios-sdk v7 now requires that apps use the swift interfaces -https://github.com/facebook/facebook-ios-sdk/blob/master/CHANGELOG.md#700

Add a .swift file to your project to embed the swift standard libs. See the repo's example app for reference - https://github.com/facebook/react-native-fbsdk/blob/master/example/ios/RNFBSDKExample/File.swift

a-metta · 2020-05-27T20:43:26Z

is it possible to add this to the documentation as a setup step? lost a whole day on this

tolik85 · 2020-05-30T12:11:55Z

How come such a show stopper requirement isn't in bold in the installation steps?

ParshantArora · 2020-06-07T14:06:17Z

PLease add this in the documentation
Create a swift file in main project and add the following code to the same

File.swift
//
// File.swift
// RNFBSDKExample
//
import Foundation

patavee · 2020-06-16T04:46:45Z

Just to note, you have to put File.swift in the folder ios and open Xcode then select the menu Product > Clean before I can successfully build it again.

Solves this issues: facebookarchive#755 facebookarchive#757

ramirobg94 · 2020-06-20T16:36:19Z

I added this PR to improve the readme, #767

cglacet · 2020-06-23T14:55:48Z

@AndrewJack, I'm not sure to get it, do we need to have only File.swift or File.swift together with AppDelegate.swift, SceneDelegate.swift as described in section 3 (I'll quote the section because I feel it states is quite unstable, for example the documentation talks about section 3 and 4 when it seems it wants to talk about 2 and 3, anyway)?

Step 3: Connect the App Delegate

Replace the code in AppDelegate.swift with the following code. This code initializes the SDK when your app launches, and allows the SDK handle results from the native Facebook app when you perform a Login or Share action:

//  AppDelegate.swift

import UIKit
import FBSDKCoreKit

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    
    func application(
        _ application: UIApplication,
        didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
    ) -> Bool {
          
        ApplicationDelegate.shared.application(
            application,
            didFinishLaunchingWithOptions: launchOptions
        )

        return true
    }
          
    func application(
        _ app: UIApplication,
        open url: URL,
        options: [UIApplication.OpenURLOptionsKey : Any] = [:]
    ) -> Bool {

        ApplicationDelegate.shared.application(
            app,
            open: url,
            sourceApplication: options[UIApplication.OpenURLOptionsKey.sourceApplication] as? String,
            annotation: options[UIApplication.OpenURLOptionsKey.annotation]
        )

    }  

}

If you are using iOS 13 or above please add the following method to your SceneDelegate:

//  SceneDelegate.swift

func scene(_ scene: UIScene, openURLContexts URLContexts: Set<UIOpenURLContext>) {
    guard let url = URLContexts.first?.url else {
        return
    }

    ApplicationDelegate.shared.application(
        UIApplication.shared,
        open: url,
        sourceApplication: nil,
        annotation: [UIApplication.OpenURLOptionsKey.annotation]
    )
}

I wonder why installing these dependencies is so hard and confusing.

cglacet · 2020-06-24T10:11:29Z

I managed to make it work following another installation process: steps 3 and 4 here(only found this french but that should do):

Étape 3 : configurer info.plist

Dans Xcode, faites un clic droit sur le fichier Info.plist de votre projet et sélectionnez Open As -> Source Code.

Insérez l’extrait XML suivant dans le corps de votre fichier juste avant le dernier élément .
<key>CFBundleURLTypes</key>
<array>
  <dict>
    <key>CFBundleURLSchemes</key>
    <array>
      <string>fb{your-app-id}</string>
    </array>
  </dict>
</array>
<key>FacebookAppID</key>
<string>{your-app-id}</string>
<key>FacebookDisplayName</key>
<string>{your-app-name}</string>
<key>LSApplicationQueriesSchemes</key>
<array>
  <string>fbapi</string>
  <string>fb-messenger-share-api</string>
  <string>fbauth2</string>
  <string>fbshareextension</string>
</array>
Remplacez {your-app-id} et {your-app-name} par le nom et l’App ID de votre app indiqués dans l’Espace App Facebook.

Étape 4 : Connecter l’App Delegate

Pour post-traiter les résultats des actions nécessitant de passer à l’application native Facebook ou à Safari, telles que Facebook Login ou les boîtes de dialogue Facebook, vous devez connecter votre classe AppDelegate à l’objet FBSDKApplicationDelegate. Pour ce faire, ajoutez le code suivant à votre fichier AppDelegate.m.
//  AppDelegate.m
#import <FBSDKCoreKit/FBSDKCoreKit.h>

- (BOOL)application:(UIApplication *)application 
    didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  
  // You can skip this line if you have the latest version of the SDK installed
  [[FBSDKApplicationDelegate sharedInstance] application:application
    didFinishLaunchingWithOptions:launchOptions];
  // Add any custom logic here.
  return YES;
}

- (BOOL)application:(UIApplication *)application 
            openURL:(NSURL *)url 
            options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options {

  BOOL handled = [[FBSDKApplicationDelegate sharedInstance] application:application
    openURL:url
    sourceApplication:options[UIApplicationOpenURLOptionsSourceApplicationKey]
    annotation:options[UIApplicationOpenURLOptionsAnnotationKey]
  ];
  // Add any custom logic here.
  return handled;
}

So there is no AppDelegate.swift but instead you need to modify AppDelegate.m. At least not for me. What a mess lol.

LuisMendoza7 · 2020-06-26T22:19:21Z

I'm having the same issue and followed the same steps to build this.

create a swift file and put into ios folder
clean build

but still i'm getting the same errors, do anyone have managed to successfully build it?

cglacet · 2020-06-28T09:10:57Z

@LuisMendoza7 Using the aforementioned build steps I managed to make it work. I only found this out of luck because I'm french (couldn't find these steps in the english version). There is a serious documentation problem for this install (links instead of a clear description).

stelselim · 2020-06-28T13:52:14Z

I'm having the same issue and followed the same steps to build this.

create a swift file and put into ios folder

clean build

but still i'm getting the same errors, do anyone have managed to successfully build it?

Did same but did not work using >0.60 version RN.
is The problem about AppDelegate.m?
I modified AppDelegate.m, did not work.

oailloud · 2020-07-02T14:35:52Z

In my case, I had to create the swift file following this process: https://stackoverflow.com/a/56187043/1773450 (i.e. from XCode and creating the "Bridging Header").

So to sum it up, to update the lib I had to run

yarn ugrade --latest react-native-fbsdk
cd ios
pod update FBSDKLoginKit FBSDKShareKit FBSDKCoreKit

and then

open XCode
create new file, select swift file
confirm "Create Bridging Header"
clean and build (I actually made my first build from XCode and then from react-native CLI)

I hope it helps... Good luck!

jorgeants · 2020-07-15T18:57:01Z

Thanks @oailloud! It's work for me.

AndrewKeplinger · 2020-07-17T18:47:05Z

I've done all of these steps and I'm still getting the original error from the bug report.
Compiling proper workspace, installed and updated cocoa pods, made the dummy swift file with the "Foundations" import in it, made other adjustments to xCode project generated by Unity.
I'm assuming that the messages "Could not find or use auto-linked library" directly leads to all of the undefined symbols.
I'm guessing that the libraries are being generated or exist somewhere and the app just isn't finding them. I'm going to try hunting them down now.

waqaramjad · 2020-07-23T22:53:56Z

do we only have to create a .swift file and nothing written in it? what code I have to put in that file?

haveamission · 2020-07-24T00:09:18Z

@waqaramjad Empty Swift file seems to work just fine

joarwilk · 2020-07-24T14:20:40Z

It's important that you create the file in XCode and not manually. It will generate a second file called <projectname>-Bridging-Header.h. Seems like it's needed

AndrewKeplinger · 2020-07-24T14:54:36Z

I created the file using Xcode. I'm still not able to compile. I get about 100 errors after the warnings in this original bug report. Can't compile, not idea what to do next.

captaincole · 2020-08-02T19:55:01Z

This solution helped me when I upgraded RN v0.62.2 but then I ran into a similar issue when I upgraded again to RN v0.63.2

Specifically, I'm only seeing 3 libraries from the fbsdk that are failing to be found

ld: warning: Could not find or use auto-linked library 'swiftWebKit'
ld: warning: Could not find or use auto-linked library 'swiftCoreMIDI'
ld: warning: Could not find or use auto-linked library 'swiftUniformTypeIdentifiers'

This is with react-native-fbsdk@2.0.0

raynox · 2020-09-09T14:00:02Z

I'm also struggling with that issue, first I had that issue when I was installing react-native-fbsdk with react-native: 62.2, I fixed that simply by adding a File.swift using Xcode. Then I tried to update react-native to 63.2 and I ran into that issue again, but this time nothing helps.

lkw1830 · 2020-09-10T16:34:27Z

I'm also struggling with that issue, first I had that issue when I was installing react-native-fbsdk with react-native: 62.2, I fixed that simply by adding a File.swift using Xcode. Then I tried to update react-native to 63.2 and I ran into that issue again, but this time nothing helps.

same issue here.

PolGuixe · 2020-09-18T15:24:38Z

I'm also struggling with that issue, first I had that issue when I was installing react-native-fbsdk with react-native: 62.2, I fixed that simply by adding a File.swift using Xcode. Then I tried to update react-native to 63.2 and I ran into that issue again, but this time nothing helps.

Same issue here...

asukhariev · 2020-09-19T12:13:20Z

Getting this error on 63.2. Anybody found how to debug and solve? thanks

2xSamurai · 2020-09-21T09:04:31Z

@oailloud Thank you.

for me this was enough.

open XCode (workspace file)
Right click project name and add a new swift file leave it as File.swift
confirm "Create Bridging Header"
clean and build

In my case, I had to create the swift file following this process: https://stackoverflow.com/a/56187043/1773450 (i.e. from XCode and creating the "Bridging Header").

So to sum it up, to update the lib I had to run
yarn ugrade --latest react-native-fbsdk
cd ios
pod update FBSDKLoginKit FBSDKShareKit FBSDKCoreKit
and then

open XCode

create new file, select swift file

confirm "Create Bridging Header"

clean and build (I actually made my first build from XCode and then from react-native CLI)

I hope it helps... Good luck!

vrazn · 2020-09-22T03:42:43Z

The problem re-appeared in our project with the new XCode version.
In our case the build was failing because of the YourProjectTests target throwing the following three errors:

ld: warning: Could not find or use auto-linked library 'swiftWebKit'
ld: warning: Could not find or use auto-linked library 'swiftCoreMIDI'
ld: warning: Could not find or use auto-linked library 'swiftUniformTypeIdentifiers'

Deleting the .swift file (if you already had it) and adding it back following the instructions above helped.
One thing to note is that you might need to specify the YourProjectTests target when adding the file too, not just your main target.

jonathasgabriel · 2020-09-29T20:47:36Z

In my case, I had to create the swift file following this process: https://stackoverflow.com/a/56187043/1773450 (i.e. from XCode and creating the "Bridging Header").

So to sum it up, to update the lib I had to run
yarn ugrade --latest react-native-fbsdk
cd ios
pod update FBSDKLoginKit FBSDKShareKit FBSDKCoreKit
and then

open XCode

create new file, select swift file

confirm "Create Bridging Header"

clean and build (I actually made my first build from XCode and then from react-native CLI)

I hope it helps... Good luck!

Thank you @oailloud !!!

jeswcollins · 2020-10-02T16:44:27Z

@emilioheinz If you already have a .swift file, try deleting it. Xcode didn't prompt me either I think because I had already tried making my own .swift file in a different folder. After I deleted it and made the file again in Xcode I was prompted for the header file.

ghost · 2020-10-02T22:27:23Z

I've created the file manually

Biplovkumar · 2020-10-03T06:55:06Z

@oailloud thanks. It helped.

d3f0lt-code · 2020-10-05T16:15:05Z

@emilioheinz when creating the file. Try to check in the targets the tests. Sample MyUpTests. check it.

Solves this issues: #755 #757

christinasund · 2020-12-09T19:56:05Z

I tried all the solutions above and none worked. Then I tried:

Open example.xcworkspace
Clean (Command + Shift + K + Option)
Delete derived data
Run the project in Xcode (should succeed)

I am now able to run successfully using yarn ios

Keep in mind I had already added the .swift file and bridging header.

Hope this helps someone else!

TheFunktory · 2020-12-14T03:28:51Z

@bernica That's probably because you already created it once and deleted it. The file gets removed but the build settings configuration persists. Search your target's build settings for "Objective-C Bridging Header"

I'm in the same boat as @emilioheinz. I'm not prompted to do"Create Bridging Header". I searched for that build setting configuration and it is empty. Any advice from here?

raboija · 2020-12-30T17:21:17Z

Same issue as @TheFunktory and @emilioheinz. Did you find a solution?

ghost · 2020-12-30T17:36:43Z

The problem re-appeared in our project with the new XCode version.
In our case the build was failing because of the YourProjectTests target throwing the following three errors:
ld: warning: Could not find or use auto-linked library 'swiftWebKit'
ld: warning: Could not find or use auto-linked library 'swiftCoreMIDI'
ld: warning: Could not find or use auto-linked library 'swiftUniformTypeIdentifiers'
Deleting the .swift file (if you already had it) and adding it back following the instructions above helped.
One thing to note is that you might need to specify the YourProjectTests target when adding the file too, not just your main target.

@raboija That solved the issue for me

marcpope · 2021-01-01T14:45:01Z

Creating File.swift in my main project folder fixed the issue for me... it auto created the (ProjectName)-Bridging-Header.h file, which appears to be empty.

ghost · 2021-01-02T15:09:02Z

In some cases (idk why) the Bridging-Header file is not auto created, creating it manually solved it for me.

maluramichael · 2021-01-02T16:22:07Z

Adding a .swift file + generating the Bridging Headers fixt our problems. Thank you @AndrewJack

rosortoa · 2021-01-11T17:59:55Z

In my case, I had to create the swift file following this process: https://stackoverflow.com/a/56187043/1773450 (i.e. from XCode and creating the "Bridging Header").

So to sum it up, to update the lib I had to run
yarn ugrade --latest react-native-fbsdk
cd ios
pod update FBSDKLoginKit FBSDKShareKit FBSDKCoreKit
and then

open XCode

create new file, select swift file

confirm "Create Bridging Header"

clean and build (I actually made my first build from XCode and then from react-native CLI)

I hope it helps... Good luck!

Thanks @oailloud

igristov · 2021-02-11T01:00:09Z

When you create a new swift file in XCode via File/New menu make sure you select the checkbox corresponding your Target project. Otherwise you will not be prompted for Bridging Header creation and xxx-Bridging-Header.h file will not get created.

kuznetsov-online · 2021-02-28T17:35:25Z

alternative 'file.swift' solution for Podfile

    installer.aggregate_targets.first.user_project.native_targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['LIBRARY_SEARCH_PATHS'] = ['$(inherited)', '$(SDKROOT)/usr/lib/swift']
      end
    end
    installer.aggregate_targets.first.user_project.save

ngocdaothanh · 2021-03-19T06:16:11Z

In case you see the issue after updating React Native from 0.63.x to 0.64.x, try this solution:

Create a new 0.64.x project, for example:

npx react-native init MyApp --template react-native-template-typescript

Compare package.json of the new project and of your old 0.63.x project, and modify the old one.
Do similarly with ios/Podfile.
Run yarn install or npm install.
Run pod install in ios directory. Probably you need to remove the old Podfile.lock file.
Now, when you rebuild your project, hopefully the issue will be fixed.

iamvucms · 2021-03-30T10:52:11Z

In my case, I had to create the swift file following this process: https://stackoverflow.com/a/56187043/1773450 (i.e. from XCode and creating the "Bridging Header").

So to sum it up, to update the lib I had to run
yarn ugrade --latest react-native-fbsdk
cd ios
pod update FBSDKLoginKit FBSDKShareKit FBSDKCoreKit
and then

open XCode

create new file, select swift file

confirm "Create Bridging Header"

clean and build (I actually made my first build from XCode and then from react-native CLI)

I hope it helps... Good luck!

Thanks a lot bro

a-metta mentioned this issue May 27, 2020

iOS build failed #753

Closed

evilchis94 mentioned this issue Jun 2, 2020

Apple Mach-O Linker Error #757

Open

ramirobg94 added a commit to ramirobg94/react-native-fbsdk that referenced this issue Jun 20, 2020

facebook-ios-sdk v7 need a swift file

88ed840

Solves this issues: facebookarchive#755 facebookarchive#757

ramirobg94 mentioned this issue Jun 20, 2020

facebook-ios-sdk v7 need a swift file #767

Merged

haroldh17 mentioned this issue Aug 3, 2020

iOS does not build passionui/support#16

Closed

janicduplessis pushed a commit that referenced this issue Nov 4, 2020

facebook-ios-sdk v7 need a swift file (#767)

b791efe

Solves this issues: #755 #757

craigrouse mentioned this issue Feb 12, 2021

File missing from dependency Tealium/tealium-react-native#67

Closed

vongohren mentioned this issue Mar 10, 2021

Crash between older setups and this lib because of swift. mixpanel/mixpanel-react-native#33

Closed

eqlion mentioned this issue Mar 12, 2021

Ios Linking problems naoufal/react-native-payments#276

Open

ravi-poonia mentioned this issue Apr 15, 2021

iOS build fail: Undefined symbols for architecture x86_64 react-native-text-input-mask/react-native-text-input-mask#209

Closed

vj-raghavan mentioned this issue Apr 19, 2021

iOS Project Doesnt Build after including the mixpanel package. mixpanel/mixpanel-react-native#38

Closed

This was referenced Jul 31, 2021

Road to v0.65.0 - RC3 phase react-native-community/releases#238

Closed

Apple Silicon (M1) troubleshooting guide (RN 0.64/0.65/0.66) facebook/react-native#31941

Closed

laikmosh mentioned this issue Nov 17, 2021

Fix Problem with M1 Macs mmazzarolo/react-native-universal-monorepo#30

Merged

patlux mentioned this issue Feb 28, 2022

Could not find or use auto-linked library 'swiftWebKit' lottie-react-native/lottie-react-native#739

Closed

dk-jlew mentioned this issue Jan 11, 2023

Binding project errors: MT5209 : Native linking error relating to standard swift libraries. xamarin/xamarin-macios#17179

Closed

ilia-shipitsin mentioned this issue Nov 20, 2023

macos Linking Swift: Undefined symbols for architecture x86_64 actions/runner-images#8843

Closed

10 tasks

TranTrieuLamQuynh mentioned this issue Mar 25, 2024

compile error：Could not find or use auto-linked library 'swiftCompatibility50': library 'swiftCompatibility50' not found firebase/firebase-ios-sdk#12603

Closed

Could not find or use auto-linked library '..." #755

Could not find or use auto-linked library '..." #755

Comments

haveamission commented May 24, 2020

🐛 Bug Report

To Reproduce

Expected Behavior

Environment

AndrewJack commented May 26, 2020 • edited Loading

a-metta commented May 27, 2020

tolik85 commented May 30, 2020

ParshantArora commented Jun 7, 2020

patavee commented Jun 16, 2020

ramirobg94 commented Jun 20, 2020

cglacet commented Jun 23, 2020

Step 3: Connect the App Delegate

cglacet commented Jun 24, 2020 • edited Loading

Étape 3 : configurer info.plist

Étape 4 : Connecter l’App Delegate

LuisMendoza7 commented Jun 26, 2020

cglacet commented Jun 28, 2020

stelselim commented Jun 28, 2020

oailloud commented Jul 2, 2020 • edited Loading

jorgeants commented Jul 15, 2020 • edited Loading

AndrewKeplinger commented Jul 17, 2020

waqaramjad commented Jul 23, 2020

haveamission commented Jul 24, 2020

joarwilk commented Jul 24, 2020

AndrewKeplinger commented Jul 24, 2020

captaincole commented Aug 2, 2020 • edited Loading

raynox commented Sep 9, 2020

lkw1830 commented Sep 10, 2020

PolGuixe commented Sep 18, 2020

asukhariev commented Sep 19, 2020

2xSamurai commented Sep 21, 2020

vrazn commented Sep 22, 2020

jonathasgabriel commented Sep 29, 2020

jeswcollins commented Oct 2, 2020

ghost commented Oct 2, 2020

Biplovkumar commented Oct 3, 2020

d3f0lt-code commented Oct 5, 2020

christinasund commented Dec 9, 2020

TheFunktory commented Dec 14, 2020 • edited Loading

raboija commented Dec 30, 2020

ghost commented Dec 30, 2020

marcpope commented Jan 1, 2021 • edited Loading

ghost commented Jan 2, 2021

maluramichael commented Jan 2, 2021

rosortoa commented Jan 11, 2021

igristov commented Feb 11, 2021

kuznetsov-online commented Feb 28, 2021

ngocdaothanh commented Mar 19, 2021

iamvucms commented Mar 30, 2021

AndrewJack commented May 26, 2020 •

edited

Loading

cglacet commented Jun 24, 2020 •

edited

Loading

oailloud commented Jul 2, 2020 •

edited

Loading

jorgeants commented Jul 15, 2020 •

edited

Loading

captaincole commented Aug 2, 2020 •

edited

Loading

TheFunktory commented Dec 14, 2020 •

edited

Loading

marcpope commented Jan 1, 2021 •

edited

Loading