0.71 how to avoid RCTAppDelegate and switch back to old way #35818

billnbell · 2023-01-13T08:09:54Z

Description

I want to upgrade to 0.71.

But I have custom PROTOCOLS...

@interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate, RNAppAuthAuthorizationFlowManager, UNUserNotificationCenterDelegate>

How do I ignore RCTAppDelegate and use my own UIResponders?

My build cannot find : RCTAppSetupPrepareApp(application);

I get no found on build.

Version

0.71.0

Output of `npx react-native info`

no

Steps to reproduce

RCTAppDelegate just remove from AppDelegate

Snack, code example, screenshot, or link to a repository

no

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

cipolleschi · 2023-01-16T11:32:31Z

Hi @billnbell There are different solutions to your problem.
One thing you can try is actually to replace UIResponder with RCTAppDelegate

-@interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate, RNAppAuthAuthorizationFlowManager, UNUserNotificationCenterDelegate>
+@interface AppDelegate : RCTAppDelegate <UIApplicationDelegate, RCTBridgeDelegate, RNAppAuthAuthorizationFlowManager, UNUserNotificationCenterDelegate>

RCTAppDelegate extends UIResponder, so you can use it instead of UIResponder.
This is the suggested approach as it will allow you to benefit for future updates for free: if we change something internally in the RCTAppDelegate, you won't have to do anything manually to migrate to the new version and will benefit from the changes.

On the other end, RCTAppDelegate is completely optional. You don't need to use it. If you don't want it, just keep your old implementation and everything should work as before. But you will have to always do some manual steps to migrate your app.

Let me know if it works.

billnbell · 2023-01-16T21:22:20Z

OK - do I need all or just the new ones? I did the following and it appeared to work ok ?

I dropped UIApplicationDelegate, RCTBridgeDelegate

#import <RCTAppDelegate.h>
#import <UIKit/UIKit.h>

#import <UserNotifications/UNUserNotificationCenter.h>
#import "RNAppAuthAuthorizationFlowManager.h"

@interface AppDelegate : RCTAppDelegate <RNAppAuthAuthorizationFlowManager, UNUserNotificationCenterDelegate>

@property (nonatomic, weak) id<RNAppAuthAuthorizationFlowManagerDelegate>authorizationFlowManagerDelegate;

@property (nonatomic, strong) UIWindow *window;

@end

cipolleschi · 2023-01-17T09:44:15Z

I dropped UIApplicationDelegate, RCTBridgeDelegate

Yep, you can drop these as RCTAppDelegate implements them already.

do I need all or just the new ones?

What do you mean with all and just the new ones? 😅 Sorry, but I'm not sure I'm following here...

I did the following and it appeared to work ok ?

The changes looks good to me. What you should also do is to remove all the implementation code that you may have in your AppDelegate.mm and that we moved to the RCTAppDelegate.mm (the same code the upgrade-helper show you to remove, basically - here and ⌘+f for AppDelegate.mm to see all the removed code.)
All that code has been moved to the RCTAppDelegate, so you can safely remove it from your app as soon as you remember to call the methods on the super class, for example

// In your AppDelegate.mm
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  // Replace `HelloWorld` with the name of your app
  self.moduleName = @"HelloWorld";
  // put all your initialization code here
  // ...
  // Remember to invoke super to initialize React Native.
  return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

Let me know if it works!

Dhimassudaryanta · 2023-02-23T06:18:18Z

Hi @billnbell There are different solutions to your problem. One thing you can try is actually to replace UIResponder with RCTAppDelegate
-@interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate, RNAppAuthAuthorizationFlowManager, UNUserNotificationCenterDelegate>
+@interface AppDelegate : RCTAppDelegate <UIApplicationDelegate, RCTBridgeDelegate, RNAppAuthAuthorizationFlowManager, UNUserNotificationCenterDelegate>
RCTAppDelegate extends UIResponder, so you can use it instead of UIResponder. This is the suggested approach as it will allow you to benefit for future updates for free: if we change something internally in the RCTAppDelegate, you won't have to do anything manually to migrate to the new version and will benefit from the changes.

On the other end, RCTAppDelegate is completely optional. You don't need to use it. If you don't want it, just keep your old implementation and everything should work as before. But you will have to always do some manual steps to migrate your app.

Let me know if it works.

This is work, thank you very much!

TomarVidhi04 · 2023-04-19T08:39:13Z

Hi @billnbell There are different solutions to your problem. One thing you can try is actually to replace UIResponder with RCTAppDelegate
-@interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate, RNAppAuthAuthorizationFlowManager, UNUserNotificationCenterDelegate>
+@interface AppDelegate : RCTAppDelegate <UIApplicationDelegate, RCTBridgeDelegate, RNAppAuthAuthorizationFlowManager, UNUserNotificationCenterDelegate>
RCTAppDelegate extends UIResponder, so you can use it instead of UIResponder. This is the suggested approach as it will allow you to benefit for future updates for free: if we change something internally in the RCTAppDelegate, you won't have to do anything manually to migrate to the new version and will benefit from the changes.
On the other end, RCTAppDelegate is completely optional. You don't need to use it. If you don't want it, just keep your old implementation and everything should work as before. But you will have to always do some manual steps to migrate your app.
Let me know if it works.
This is work, thank you very much!

i am facing same problem RCTAppDelegate.h file not found

cipolleschi · 2023-04-19T09:28:04Z

@TomarVidhi04 hi there! Just to make sure that the setup is correct: did you update React Native, run Yarn and reinstall the pods with bundle exec pod install?

It could be that you forgot one of the above steps and React Native did not downloaded the file.

To make sure about that, can you check whether in the Pods project, Development Pods, you have a folder called React-AppDelegate and that it contains that header?

tomwanzek · 2023-04-28T00:33:11Z

@TomarVidhi04 As for the RCTAppDelegate.h file not found when building issue, I might have a suggestion to check:

Is it possible to build the project from the command line with yarn ios? If so and the matter is purely an Xcode build issue, then it may simply be the following:

Make sure to open the workspace (xcworkspace file) in Xcode, not just the project for the app itself. The workspace includes the

Pods project, Development Pods

with the React-RCTAppDelegate directory w/ header files and all the trimmings as mentioned by @cipolleschi 😄

If you opened only the xcodeproj file with XCode it won't find the pods project.

Once you build the project from within the opened workspace, it should be fine. Hopefully that does the trick. 🤞

ucheNkadiCode · 2023-05-05T12:45:54Z

From your advice, I actually looked at my Pods -> Development Pods and saw that after upgrading from RN 0.69.10 -> 71.7 I actually was missing my React-RCTAppDelegate pod.

After that I tried pod deintegrate then pod install

But I'm still getting

'React/RCTEventEmitter.h' file not found and RCTAppDelegate.h file not found . I literally see RCTAppDelegate.h right there but it says it's not found. I'm unsure of why RCT-EventEmitter is also not being found all of a sudden

Also, even in RCTAppDelegate pod, RCTBridge.h is not being found

please help when you can. Is there an earlier version of 71 that might work for M1?

cipolleschi · 2023-05-05T13:50:00Z

Hi @ucheNkadiCode. Version 0.71.7 works properly. There is something dirty in your system.

Please try to:

cd <yourApp>
yarn // <--- to make sure that you have the most updated scripts
rm <yourApp>/ios/build // <-- Remove the build folder created by codegen
cd ios
pod install

At this point, you should have the most recent scripts, a clean situation and the most recent pods for your version.

Let me know if this works!

ucheNkadiCode · 2023-05-05T23:31:14Z

Hey @cipolleschi Thank for your help!

Now my app is able to properly find RCTApp delegate! for some reason however,

In my AppName-Bridging-Header I'm still seeing 'react/RCTEventEmitter.h file not found'. It's also still not in my react pods either

cipolleschi · 2023-05-09T10:11:21Z

Hi @ucheNkadiCode, I think you can safely remove that line from the the bridging headers. We are not generating that file, Cocoapods/Xcode does that automatically. So, probably, it has been generated when you were having trouble compiling/building. Let's try to remove the line and see what happens.

You should also have that file, though. It should be in the Development Pods/React-Core/Default/Modules path:

This is a new App I created from 0.71.7.

anhdo9797 · 2023-06-23T03:18:52Z

Hi @ucheNkadiCode. Version 0.71.7 works properly. There is something dirty in your system.

Please try to:

cd <yourApp>

yarn // <--- to make sure that you have the most updated scripts

rm <yourApp>/ios/build // <-- Remove the build folder created by codegen

cd ios

pod install

At this point, you should have the most recent scripts, a clean situation and the most recent pods for your version.

Let me know if this works!

Hi @cipolleschi, I have applied all your solutions but it doesn't work. Can you give me more solutions?

I upgraded React native version from 0.64 to 0.7.18. I have no problem in Pod/Development Pod/React-RCT

but I get an error 'RCTAppDelegate.h' file not found in my AppDelegate.h

This is my Podfile:

project ‘MyApp’,
        'Debug' => :debug,
        'QARelease' => :release,
        'Release' => :release

target 'MyApp' do

  config = use_native_modules!
  
  # Flags change depending on the env values.
  flags = get_default_flags()

  # This has to come before use_react_native or you get AppDelegate or RCTEventEmitter not found
  use_frameworks! :linkage => :static

  use_react_native!(
    :path => config[:reactNativePath],
    # Hermes is now enabled by default. Disable by setting this flag to false.
    # Upcoming versions of React Native may rely on get_default_flags(), but
    # we make it explicit here to aid in the React Native upgrade process.
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
    :flipper_configuration => flipper_config,
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  pod 'FirebaseCore', :modular_headers => true
  pod 'FirebaseCoreExtension', :modular_headers => true
  pod 'FirebaseInstallations', :modular_headers => true
  pod 'GoogleDataTransport', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  pod 'nanopb', :modular_headers => true

  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end
  
end

cipolleschi · 2023-06-23T10:58:40Z

Hi @anhdo9797.

First of all, notice that Flipper is incompatible with frameworks, so you'd have to set this:
:flipper_configuration => FlipperConfiguration.disabled

Then, I did some tests:

created a new app from the latest version of 0.71 (which is 0.71.10)
installed pods with USE_FRAMEWORKS=static NO_FLIPPER=1 bundle exec pod install => the error appeared but then Xcode was able to resolve it and the build was successful
changed the podfile adding use_frameworks! :linkage => :static before use_react_native!
reinstalled the pods with NO_FLIPPER=1 bundle exec pod install
cleaned the project with ⌘⇪K
Rebuild, and it worked.

I'm start thinking that the problem could come from some of your dependency, as a vanilla project works as expected.

As tentative test, given that I cant repro it locally, could you try to apply this change in your AppDelegate.h file?

-#import <RCTAppDelegate.h>
+#import <React_RCTAppDelegate/RCTAppDelegate.h>

In theory, Xcode should be able to resolve the <RCTAppDelegate.h>, but it may need some help if some dependency is messing with the search paths.

anhdo9797 · 2023-06-28T10:27:39Z

Hi @anhdo9797.

First of all, notice that Flipper is incompatible with frameworks, so you'd have to set this: :flipper_configuration => FlipperConfiguration.disabled

Then, I did some tests:

created a new app from the latest version of 0.71 (which is 0.71.10)

installed pods with USE_FRAMEWORKS=static NO_FLIPPER=1 bundle exec pod install => the error appeared but then Xcode was able to resolve it and the build was successful

changed the podfile adding use_frameworks! :linkage => :static before use_react_native!

reinstalled the pods with NO_FLIPPER=1 bundle exec pod install

cleaned the project with ⌘⇪K

Rebuild, and it worked.

I'm start thinking that the problem could come from some of your dependency, as a vanilla project works as expected.

As tentative test, given that I cant repro it locally, could you try to apply this change in your AppDelegate.h file?
-#import <RCTAppDelegate.h>
+#import <React_RCTAppDelegate/RCTAppDelegate.h>
In theory, Xcode should be able to resolve the <RCTAppDelegate.h>, but it may need some help if some dependency is messing with the search paths.

Thank @cipolleschi, It works for me

enisinanaj · 2023-07-04T12:39:11Z

2. USE_FRAMEWORKS=static NO_FLIPPER=1 bundle exec pod install

I have the exact same issue. I upgraded from 0.69 to 0.71 and I'm continuously having this issue for iOS. Android works fine.
I checked the header search paths and it should be all fine.

Since I'm also using Firebase via the react-native-firebase project I cannot use Flipper as I need to use frameworks.

I see React-AppDelegate project in my pods directory.
I tried step by step what you wrote here but I still get the issue. Do you have please any other hints?

Cheers!

cipolleschi · 2023-07-04T13:52:43Z

Can you try to use this import statement in your AppDelegate?

-#import <RCTAppDelegate.h>
+#import <React_RCTAppDelegate/RCTAppDelegate.h>

enisinanaj · 2023-07-04T14:37:59Z

Same error with his change as well unfortunately.

cipolleschi · 2023-07-04T15:11:03Z

could you try to set up a minimal reproducer using this repo This is a recurring problem, so I really want to solve it once and for all, but not using Firebase directly, I don't know which steps to follow to reproduce it.

enisinanaj · 2023-07-04T15:14:44Z

i will try to do that. But generally a new project with the same rn version 0.71 worked fine when i tried some weeks ago.

enisinanaj · 2023-07-18T22:40:29Z

Hi, I cannot reproduce it with the repo or a new project. After adding all my dependencies it just builds and runs.
I checked and double-checked all search paths, deintegrated the pods and installed them again but I'm having the same issue.
Any other ideas please?

billnbell · 2023-07-19T04:29:01Z

USE_FRAMEWORKS=static NO_FLIPPER=1 bundle exec pod install

I have the exact same issue. I upgraded from 0.69 to 0.71 and I'm continuously having this issue for iOS. Android works fine. I checked the header search paths and it should be all fine.

Since I'm also using Firebase via the react-native-firebase project I cannot use Flipper as I need to use frameworks.

I see React-AppDelegate project in my pods directory. I tried step by step what you wrote here but I still get the issue. Do you have please any other hints?

Cheers!

Bust open Xcode and build from there. Most of the time it will give you more errors.

billnbell · 2023-07-19T04:29:42Z

Hi, I cannot reproduce it with the repo or a new project. After adding all my dependencies it just builds and runs.
I checked and double-checked all search paths, deintegrated the pods and installed them again but I'm having the same issue.
Any other ideas please?

I know it sounds stupid - but reboot.

enisinanaj · 2023-07-19T08:50:10Z

Hi, I cannot reproduce it with the repo or a new project. After adding all my dependencies it just builds and runs.
I checked and double-checked all search paths, deintegrated the pods and installed them again but I'm having the same issue.
Any other ideas please?

I know it sounds stupid - but reboot.

I had hopes about this but seems to have no effect :(

enisinanaj · 2023-07-19T08:51:25Z

Hi, I cannot reproduce it with the repo or a new project. After adding all my dependencies it just builds and runs.
I checked and double-checked all search paths, deintegrated the pods and installed them again but I'm having the same issue.
Any other ideas please?

I know it sounds stupid - but reboot.

tried building both from the command line and from xcode. but I have the same issue... am I right in assuming that it has something to do with the search paths?

cipolleschi · 2023-07-20T12:39:47Z

Not really, it has to do with how Xcode packages the frameworks and where the files are put. which influences the header search path, but that's not the root cause.

do you have this line in your app header_search_paths?

Are you using pnpm or plain npm?
Do you have these folders in your derived data?

Is this the only error you are seeing in the build? Sometimes there are multiple errors and those are the actual responsible for the error (for example, another framework can't be build, so RCTAppDelegate can't be build and the app can't find the header).
Are you using also swift, maybe? In some cases the Objective-C/Swift interop may create issues and therefore we can have to use a different import (look here for more info)

enisinanaj · 2023-07-20T23:30:09Z

Not really, it has to do with how Xcode packages the frameworks and where the files are put. which influences the header search path, but that's not the root cause.

do you have this line in your app header_search_paths?

2. Are you using pnpm or plain npm? 3. Do you have these folders in your derived data? 4. Is this the only error you are seeing in the build? Sometimes there are multiple errors and those are the actual responsible for the error (for example, another framework can't be build, so RCTAppDelegate can't be build and the app can't find the header). 5. Are you using also swift, maybe? In some cases the Objective-C/Swift interop may create issues and therefore we can have to use a different import (look [here](https://github.com/react-native-community/RNNewArchitectureLibraries/issues/15) for more info)

Hi @cipolleschi, first of all thanks a lot for the detailed input.

Yes I do have that line.
Just plain npm
No that I don't have
Building from Xcode that is the only error. While building from the command line I had a second one about Firebase
After some investigation then I came across 'FirebaseCore/FIRAnalyticsConfiguration.h' file not found on v5 invertase/react-native-firebase#1106 (comment) so I removed use_frameworks from the podfile and followed your initial guide. I had to do some further adjustments but finally, I managed to run it (on a real device). On the simulator, I still have the same issue but I can figure it out from here (I think).
I am also using Swift but that works as looks like

cipolleschi · 2023-07-21T09:57:50Z

If you managed to run it on a real device but not a simulator, try to cleanup the derived data. It could be that Xcode has something cached for the simulator builds that makes those build fail.

zinzaducnm · 2023-09-27T04:56:38Z

In my case, I created multiple targets, and header search paths of these target missed some value for example "${PODS_CONFIGURATION_BUILD_DIR}/React-RCTAppDelegate/React_RCTAppDelegate.framework/Headers"
I try to create abstract_target, my targets are inside the abstract_target.
Remember to remove Pods/, Podfile.lock, and pod install again then I can build without any error.
Hope this helps!

jpouabou · 2023-11-28T22:39:14Z

Hi,

I have literally tried every solution there is on GitHub and stack overflow regarding this error and nothing works for me. I'm on 0.72.7 and I am also getting the AppDelegate.h not found issue.
I have spent 2 days on this and I am thinking about going to back to an old version before this issue arose.
I am not sure what steps to take to even attempt to solve this because every solution I have tried is not working. I am on Apple M2 Chip.

cipolleschi · 2023-11-30T13:30:01Z

Hi @jpouabou, I'm sorry you are hitting this problem.

A few questions to help you out:

If you create a new app from 0.72.7, does the problem persist?
Can you try the following:
1. Navigate to your app's ios folder, then run:
```
bundle install
bundle exec pod deintegrate
bundle exec pod install
```
1. Open the <YourAppName>.xcworkspace file
2. Try to build and see whether the problem persist
Is your app's Podfile similar to the template one?
Can you share it?
Can you share the list of 3rd party libraries you are using?
Can you post the precise error you are seeing in Xcode?

developersflex · 2023-12-01T13:29:01Z

Hello,

I'm just getting the same error but on xcode cloud. Does the above solutions work on xcode cloud?

cipolleschi · 2023-12-01T14:50:29Z

Hi @developersflex! I think it depends on the error. I have never used Xcode cloud, so I don't know what you can do on/with it.
In theory, it could/should, but this error depends more on the specific App setup (3rd party libraries not properly set up) than on React Native.

billnbell added Needs: Triage 🔍 Type: New Architecture Issues and PRs related to new architecture (Fabric/Turbo Modules) labels Jan 13, 2023

react-native-bot added the Component: Switch label Jan 13, 2023

vincicat mentioned this issue Jan 13, 2023

Creating a new project is stuck at Installing cocoapods dependencies #35819

Closed

Danushka50 mentioned this issue May 19, 2023

RCTAppDelegate.h file not found #36611

Closed

github-actions bot added the Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. label Jul 20, 2023

enisinanaj mentioned this issue Sep 8, 2023

RCTAppDelegate.h file not found after upgrading from 0.70.6 to 0.71.4 react-native-community/upgrade-support#229

Open

1 task

cortinico assigned cipolleschi Oct 27, 2023

cipolleschi closed this as completed Oct 27, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

0.71 how to avoid RCTAppDelegate and switch back to old way #35818

0.71 how to avoid RCTAppDelegate and switch back to old way #35818

billnbell commented Jan 13, 2023

cipolleschi commented Jan 16, 2023

billnbell commented Jan 16, 2023

cipolleschi commented Jan 17, 2023

Dhimassudaryanta commented Feb 23, 2023

TomarVidhi04 commented Apr 19, 2023

cipolleschi commented Apr 19, 2023

tomwanzek commented Apr 28, 2023

ucheNkadiCode commented May 5, 2023 •

edited

Loading

cipolleschi commented May 5, 2023

ucheNkadiCode commented May 5, 2023

cipolleschi commented May 9, 2023 •

edited

Loading

anhdo9797 commented Jun 23, 2023 •

edited

Loading

cipolleschi commented Jun 23, 2023 •

edited

Loading

anhdo9797 commented Jun 28, 2023

enisinanaj commented Jul 4, 2023 •

edited

Loading

cipolleschi commented Jul 4, 2023

enisinanaj commented Jul 4, 2023 •

edited

Loading

cipolleschi commented Jul 4, 2023

enisinanaj commented Jul 4, 2023

enisinanaj commented Jul 18, 2023

billnbell commented Jul 19, 2023

billnbell commented Jul 19, 2023

enisinanaj commented Jul 19, 2023

enisinanaj commented Jul 19, 2023 •

edited

Loading

cipolleschi commented Jul 20, 2023

enisinanaj commented Jul 20, 2023

cipolleschi commented Jul 21, 2023

zinzaducnm commented Sep 27, 2023 •

edited

Loading

jpouabou commented Nov 28, 2023

cipolleschi commented Nov 30, 2023

developersflex commented Dec 1, 2023

cipolleschi commented Dec 1, 2023

0.71 how to avoid RCTAppDelegate and switch back to old way #35818

0.71 how to avoid RCTAppDelegate and switch back to old way #35818

Comments

billnbell commented Jan 13, 2023

Description

Version

Output of npx react-native info

Steps to reproduce

Snack, code example, screenshot, or link to a repository

cipolleschi commented Jan 16, 2023

billnbell commented Jan 16, 2023

cipolleschi commented Jan 17, 2023

Dhimassudaryanta commented Feb 23, 2023

TomarVidhi04 commented Apr 19, 2023

cipolleschi commented Apr 19, 2023

tomwanzek commented Apr 28, 2023

ucheNkadiCode commented May 5, 2023 • edited Loading

cipolleschi commented May 5, 2023

ucheNkadiCode commented May 5, 2023

cipolleschi commented May 9, 2023 • edited Loading

anhdo9797 commented Jun 23, 2023 • edited Loading

cipolleschi commented Jun 23, 2023 • edited Loading

anhdo9797 commented Jun 28, 2023

enisinanaj commented Jul 4, 2023 • edited Loading

cipolleschi commented Jul 4, 2023

enisinanaj commented Jul 4, 2023 • edited Loading

cipolleschi commented Jul 4, 2023

enisinanaj commented Jul 4, 2023

enisinanaj commented Jul 18, 2023

billnbell commented Jul 19, 2023

billnbell commented Jul 19, 2023

enisinanaj commented Jul 19, 2023

enisinanaj commented Jul 19, 2023 • edited Loading

cipolleschi commented Jul 20, 2023

enisinanaj commented Jul 20, 2023

cipolleschi commented Jul 21, 2023

zinzaducnm commented Sep 27, 2023 • edited Loading

jpouabou commented Nov 28, 2023

cipolleschi commented Nov 30, 2023

developersflex commented Dec 1, 2023

cipolleschi commented Dec 1, 2023

Output of `npx react-native info`

ucheNkadiCode commented May 5, 2023 •

edited

Loading

cipolleschi commented May 9, 2023 •

edited

Loading

anhdo9797 commented Jun 23, 2023 •

edited

Loading

cipolleschi commented Jun 23, 2023 •

edited

Loading

enisinanaj commented Jul 4, 2023 •

edited

Loading

enisinanaj commented Jul 4, 2023 •

edited

Loading

enisinanaj commented Jul 19, 2023 •

edited

Loading

zinzaducnm commented Sep 27, 2023 •

edited

Loading