-
-
Notifications
You must be signed in to change notification settings - Fork 69
Workaround for empty main bundle identifier on Linux #64
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
Conversation
…dentifier instead.
Codecov Report
@@ Coverage Diff @@
## main #64 +/- ##
==========================================
+ Coverage 77.95% 77.98% +0.02%
==========================================
Files 51 51
Lines 4578 4584 +6
==========================================
+ Hits 3569 3575 +6
Misses 1009 1009
Continue to review full report at Codecov.
|
@jt9897253 thanks for your contribution! Does You can uncomment these lines in the workflow for now Parse-Swift/.github/workflows/ci.yml Lines 99 to 100 in 80802c5
You can comment them back out after we see the results as Linux will still have some failures when comparing optionals in the current test cases. |
Unfortunately, not. Here's the full log for
I do not yet understand why it is "Unable to sync with parse-server".
Done |
I suspect this might actually be okay. The custom Let us know if/when you use a ParseFile in your actual development and if it works. |
Can you comment back out the Linux tests and we can merge your PR. |
I've tested downloading a parse file, the resulting path looks like
and contains the correct data. Although If this really was it, adding parse file support to Linux was way simpler than anticipated. |
On Linux, Bundle.main.bundleIdentifier is nil.
This commit creates a custom bundle identifier instead.
With this change, tests for
ParseFileManager
seem to pass on Linux:I put up this PR for discussion of what the the custom value for
Bundle.main.bundleIdentifier
should be, on Linux. Is the proposed solution unique enough?As an example, with this change, the test
ParseFileManagerTests.testWriteData
would write tofile:///$HOME/.local/share/parse/com.github.parse-community.parse-swift.applicationId/test.txt
on Linux.I do not exactly understand how this path is composed but it looks acceptable for me, as it is located in the user's home directory.
This is a follow up to the discussion from #63