Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Realm.PlatformHelpers.dll file warning (20.1.0) #3691

Open
peachypixels opened this issue Jan 16, 2025 · 5 comments
Open

Realm.PlatformHelpers.dll file warning (20.1.0) #3691

peachypixels opened this issue Jan 16, 2025 · 5 comments

Comments

@peachypixels
Copy link

What happened?

Hello!

I've just updated a Unity project from Realm (Dot Net) 12.5.0 to 20.1.0 and upon installing the Unity package (from a tarball) the following warning was displayed...

A meta data file (.meta) exists but its asset 'Packages/io.realm.unity/Runtime/Realm.PlatformHelpers.dll' can't be found. When moving or deleting files outside of Unity, please ensure that the corresponding .meta file is moved or deleted along with it.

Looking at the package cache folder here...

\Library\PackageCache\io.realm.unity@0044033add5c\Runtime

The Realm.PlatformHelpers.dll.meta file is indeed present, without its corresponding dll.

I'm assuming the dll is not required in the 20.N.N version, but the meta file is still being bundled.

I'm also guessing the presence of the meta file has zero impact, beyond the warning being displayed. But thought it worth reporting anyway.

Repro steps

Install Realm Dot Net (tarball) 20.1.0 into Unity using the Unity Package Manager.

Version

What Atlas Services are you using?

Local Database only

What type of application is this?

Unity

Client OS and version

Windows 10 (22H2)

Code snippets

No response

Stacktrace of the exception/crash you're getting

Relevant log output

@nirinchev
Copy link
Member

You're right - must have missed that file when cleaning up the sync portions of the project. Do you want to submit a PR that removes it - should be in the Realm.Unity/Runtime folder.

@peachypixels
Copy link
Author

Thanks @nirinchev

I'll do that tomorrow (or Monday) as just finishing work for the day.

@peachypixels
Copy link
Author

I tried creating a pull request (on the website) but upon submitting the following message was displayed...

Pull request creation failed. Validation failed: must be a collaborator

Selected community branch and then submitted, but maybe I did something wrong.

@nirinchev
Copy link
Member

I think you'd need to fork the repo and submit an upstream PR.

@peachypixels
Copy link
Author

Apologies, operator error :-) It seems GitHub desktop does not fork a repo on cloning, contrary to the docs.

Repo forked and PR created for the community branch.

Let me know if I did anything wrong, so I know for next time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants