Yes I know this now, but really, Harbour FAQ should have mentioned it.
A notification should have been sent out to app developers in advance
that the following commit might cause problems:
https://github.com/sailfish-sdk/libsailfishapp/commit/3febb7a2204cf13f01ab9e9ff86a84afc9b137d7
Another issue that is not directly related to this, but maybe someone at
Jolla reads this..
Harbour team has downgraded my app, SGAuth, down from v0.3-2 to v0.2-2
without any notification. So on Jolla store the latest release is v0.2-2
all of a sudden, but when I login to Harbour it shows v0.3-2 as the
latest accepted version. And it has been more than 48 hours and still no
reply from developer-care@... is this common behaviour, changing version
of the app without any notification?
On 31.1.2014 22:26, Andrey Kozhevnikov wrote:
probably you right, but system update cant check if you used empty
storage parameters in your app.
this situation should learn you write applications better from the
first lines of code :)
On 01.02.2014 02:24, Andreas Storbjörk wrote:
I wasn't the only one who missed it in that case.. so it can't have
been very obvious. And the system update should have take care of it
anyhow.
On 31.1.2014 22:20, Andrey Kozhevnikov wrote:
i think it somewhere in local storage documentation you didnt read.
On 01.02.2014 02:18, Andreas Storbjörk wrote:
There should have been a mention about this somewhere in the
documentation from the beginning.
Like when you create a new empty project, this is your .cpp:
int main(int argc, char *argv[])
{
// SailfishApp::main() will display "qml/template.qml", if you
need more
// control over initialization, you can use:
//
// - SailfishApp::application(int, char *[]) to get the
QGuiApplication *
// - SailfishApp::createView() to get a new QQuickView *
instance
// - SailfishApp::pathTo(QString) to get a QUrl to a resource
file
//
// To display the view, call "show()" (will show fullscreen on
device).
return SailfishApp::main(argc, argv);
}
Why wasn't there any mention of organizationName and
organizationDomain here?
On 31.1.2014 22:02, Andrey Kozhevnikov wrote:
i mean: if you used appName and orgName before your app not affected.
On 01.02.2014 01:44, Stefan Brand wrote:
Well, I just used the default sailfish app template from the SDK...
In an IRC-Log I saw thp mention that setting organizationName and
organizationDomain to "" will revert back to the old path. So i
changed my main() in the cpp to this:
int main(int argc, char *argv[])
{
QCoreApplication::setApplicationVersion(APP_VERSION);
// Fix move of LocalStorage in libsailfishapp
QCoreApplication::setOrganizationDomain("");
QCoreApplication::setOrganizationName("");
return SailfishApp::main(argc, argv);
}
Unfortunately this doesn't seem to work. The first line setting
the application version is working fine, but it still uses the
new storage path. What am I doing wrong here?
Am 31.01.2014 20:24, schrieb Andrey Kozhevnikov:
yes, default path was changed. you might need to set your own
applicationName, organizationName. good written apps wasnt
affected by
update ;)
https://github.com/sailfish-sdk/libsailfishapp/commit/3febb7a2204cf13f01ab9e9ff86a84afc9b137d7
On 01.02.2014 00:31, Stefan Brand wrote:
Hi there,
I just installed the latest update 1.0.3.8 to my Jolla.
Afterwards I opened SailOTP (the app I wrote) and was greeted
with an empty screen. All off my OTP-Tokens where gone.
A little investigation shows that the LocalStorage DB was moved
somehow.
Before the update it was in
/home/nemo/.local/share/harbour-sailotp/QML/...
After the update a new DB was created in
/home/nemo/.local/share/harbour-sailotp/harbour-sailotp/QML/...
Copying the old QML-folder into the second harbour-sailotp
folder brought back my tokens.
I didn't do any updates to my app, so this can only be caused
by the system update. So did anyone else see this behavior with
other apps? I think this might be a bug, so any thought on this?
Thanks in advance.
Regards
Stefan Brand
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
