-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
[macOS] "Something went wrong" when exporting #48
Comments
Thanks @pcastagnaro for reporting this. I was able to reproduce this in Can you also let me know your version? |
Hi! Thanks for asking!
I have the latest version, the 10.14.5. And the most striking is that this
error happens in my first project. I don't want to do a fresh install
because I write some information in this project and I don't want to loose
them.
El dom., 14 jul. 2019 08:55, Rishiraj Sharma <notifications@github.com>
escribió:
… Thanks @pcastagnaro <https://github.com/pcastagnaro> for reporting this.
I was able to reproduce this in Mojave 10.14.1 but not in latest version
of Mojave 10.14.5, it was working as expected.
Can you also let me know your version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#48?email_source=notifications&email_token=ACDKPJVHZDETNPRTYBVBLCLP7MH3DA5CNFSM4IDBDR2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ4D2XY#issuecomment-511196511>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACDKPJXHWKBSM5SJVURZC3LP7MH3DANCNFSM4IDBDR2A>
.
|
Don't worry, you won't loose any data (because app points a single storage file). Just keep the app open till I find a fix for this. In meantime you can go and save a copy of master file:
(you should see a |
Oh, great!
Many many many thanks! I will be expectant to the fix!
Thanks a lot again for the application and for your support!
El dom., 14 jul. 2019 09:25, Rishiraj Sharma <notifications@github.com>
escribió:
… Don't worry, you won't loose any data (because app points a single storage
file). Just keep the app open till I find a fix for this.
In meantime you can go and save a copy of master file:
/Users/<username>/Library/Application Support/Swiftness/storage
(you should see a content.json)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#48?email_source=notifications&email_token=ACDKPJXPCEABJWNEGMUU4NTP7MLMDA5CNFSM4IDBDR2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ4EJMQ#issuecomment-511198386>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACDKPJWNYUL62FU5D2WZ7X3P7MLMDANCNFSM4IDBDR2A>
.
|
Ok guys, I locate the problem, it's linked to this call: SwiftnessX/app/components/ExportDialog.js Line 117 in 7e47c8d
fs.writeFile(fileName, JSON.stringify(this.state), function (err, result) {
if (err) console.log('error', err);
}); |
Thanks @mpgn! I am pushing this hot-fix for now, will look into the problem with |
Could you release the |
Hi @pcastagnaro,
In meantime, please check the latest release to fix this issue: https://github.com/ehrishirajsharma/SwiftnessX/releases/tag/v0.2.3 Please let me know if this fixes the current issue. |
Thanks a lot @ehrishirajsharma!! |
Operating System: macOS Mojave
Describe the bug
When I create a library and then I try to export them, I get the message "Something went wrong" and the exported file doesn't create.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A JSON file created with the Library data
The text was updated successfully, but these errors were encountered: