Mac Sonoma/conflicted copies and app isn't loading

yes, I doesn't restart the app

I have exactly the same sync problem right after installing Sonoma on a Mac book pro. Conflicting copies of all folders, no files left in the original folders, and after uninstalling the Dropbox app it is impossible to get it to run again, it always crashes on launch.

I tried pretty much everything, restarting the mac, trying on the web app to fix the sync, nothing worked since now.

Waiting here for a solution.

I precise that the group with which I shared the folders and files don't see the new "conflicting copies" of any folder, but they also lose the files in the original folders.

Thanks to anyone who can help to fix the issue.

 bn.BUILD_KEY: Dropbox
bn.VERSION: 184.4.6543
bn.constants.WINDOWS_SHELL_EXT_VERSION: 66
bn.is_frozen: True
machine_id: 6c5f9e17-567b-5d6a-bf83-11b564f4ec56
pid: 1410
ppid: 1
uid: 501
user_info: pwd.struct_passwd(pw_name='jordangamet', pw_passwd='********', pw_uid=501, pw_gid=20, pw_gecos='Jordan GAMET', pw_dir='/Users/jordangamet', pw_shell='/bin/zsh')
effective_user_info: pwd.struct_passwd(pw_name='jordangamet', pw_passwd='********', pw_uid=501, pw_gid=20, pw_gecos='Jordan GAMET', pw_dir='/Users/jordangamet', pw_shell='/bin/zsh')
euid: 501
gid: 20
egid: 20
group_info: grp.struct_group(gr_name='staff', gr_passwd='*', gr_gid=20, gr_mem=['root'])
effective_group_info: grp.struct_group(gr_name='staff', gr_passwd='*', gr_gid=20, gr_mem=['root'])
DYLD_LIBRARY_PATH: None
cwd: '/'
real_path='/'
mode=0o40755 uid=0 gid=0
parent mode=0o40755 uid=0 gid=0
HOME: '/Users/jordangamet'
appdata: '/Users/jordangamet/.dropbox/instance1'
real_path='/Users/jordangamet/.dropbox/instance1'
mode=0o40700 uid=501 gid=20
parent mode=0o40755 uid=501 gid=20
dropbox_path: '/Users/jordangamet/Library/CloudStorage/Dropbox'
real_path='/Users/jordangamet/Library/CloudStorage/Dropbox'
not found
parent mode=0o40755 uid=501 gid=20
sys_executable: '/Applications/Dropbox.app/Contents/MacOS/Dropbox'
real_path='/Applications/Dropbox.app/Contents/MacOS/Dropbox'
mode=0o100755 uid=501 gid=20
parent mode=0o40755 uid=501 gid=20
trace.__file__: '/Applications/Dropbox.app/Contents/Resources/python-packages.zip/dropbox/client/ui/common/boot_error.pyc'
real_path='/Applications/Dropbox.app/Contents/Resources/python-packages.zip/dropbox/client/ui/common/boot_error.pyc'
not found
parent not found
tempdir: '/var/folders/y2/vzqy1tg937g8ybp9_6ffzb600000gn/T'
real_path='/private/var/folders/y2/vzqy1tg937g8ybp9_6ffzb600000gn/T'
mode=0o40700 uid=501 gid=20
parent mode=0o40755 uid=501 gid=20
Traceback (most recent call last):
File "desktop/dropbox/client/main.py", line 5546, in _setup_root_for_account
File "desktop/dropbox/sync_root/helpers.py", line 520, in get_root_for_account
File "desktop/dropbox/foundation/futures/basic.py", line 858, in result
File "desktop/dropbox/sync_root/handlers/macos/file_provider.py", line 232, in set_result_or_convert_exception
dropbox.mac.internal.MacError: [Errno -2001] Error Domain=NSFileProviderErrorDomain Code=-2001 "Aucun fournisseur de fichiers valide trouvé portant l’identifiant « com.getdropbox.dropbox.fileprovider/30359e90-88fb-45a4-94eb-a46a81667bdd »." UserInfo={NSLocalizedDescription=Aucun fournisseur de fichiers valide trouvé portant l’identifiant « com.getdropbox.dropbox.fileprovider/30359e90-88fb-45a4-94eb-a46a81667bdd ».}

After Sanoma update on MacBook Air, every one of my shared folders created a conflicted copy, including folders shared with me.  Unfortunately, some of the sub folders and files remained in the original folders/sub folders, and some of them were "moved" to the conflicted copy folder(s).  The really bad news is the folder shared with me actually had some of it's content moved to my personal conflicted copy folder and is no longer part of the original folder.  Thus, the organization that shared the folder with me no longer has access to the moved folders/files.  I have thousands of files/folders that are either in the original location or the conflicted copy location, but neither location has everything.  I don't want to manually move everything back from the conflicted copy to the original.  How do I fix this???  PLEASE HELP!

@Jay - Yes, but no luck. What’s really strange is that about two thirds of my files were moved from the original folder to the conflicted copy folder. I decided to manually move everything back to the original folders then delete the “CC” folders. Hopefully, it was a one-time glitch with the Sonoma update and won’t happen again.