Settings and macOS. Impossible to create a ini file...

Francky033

I modified my code this way but it still doesn't work...

QString file = QFileDialog::getSaveFileName(
		this, tr("Save a configuration file..."), QStandardPaths::writableLocation(QStandardPaths::AppLocalDataLocation), "configuration file (*.ini)");

QString d = file.left(file .lastIndexOf("/"));

QSettings::setPath(QSettings::IniFormat, QSettings::UserScope, d);

QSettings settings(file, QSettings::IniFormat);

settings.beginGroup("Data");

settings.setValue("a1", 0.0);
settings.setValue("a2", 0.0);

settings.endGroup();

return settings.status();

jsulm

@Francky033 said in Settings and macOS. Impossible to create a ini file...:

QSettings settings(file, QSettings::IniFormat);

file should be only file name here.

"QString d = file.left(file .lastIndexOf("/"));" - use QFileInfo::absolutePath() to get the folder without file name.

Francky033

jsulm, I modified my code this way, but no effect

QString file = QFileDialog::getSaveFileName(
		this, tr("Save a configuration file..."), QStandardPaths::writableLocation(QStandardPaths::AppLocalDataLocation), "configuration file (*.ini)");

QFileInfo f(file);

QString d = f.absoluteFilePath();
QString name = f.fileName();

QSettings::setPath(QSettings::IniFormat, QSettings::UserScope, d);

QSettings settings(f, QSettings::IniFormat);

settings.beginGroup("Data");

settings.setValue("a1", 0.0);
settings.setValue("a2", 0.0);

settings.endGroup();

return settings.status();

SGaist

But why are you using setPath at all ?

Francky033

I removed the setPath and I still have the same result. When I start the program from qtcreator, everything works. But it does not work anymore when the program is installed on the OS.
This seems to me to be a permissions problem. But how to solve this?

SGaist

Did you used macdeployqt before running it outside of Qt ?

artwaw

@Francky033 If it is permission problem OS should ask user upon the startup if read/write permission to folder should be granted (like it happens every time I deploy my software).
It's ok if you run it from QtCreator as child process of QtCreator is allowed standard access to the home tree.

Francky033

SGaist : Yes !

artwaw : But if it is not a problem of permissions, where can the problem come from? What also surprises me is the message "No such file or directory" that appears in the log when the settings variable is created and the NoERROR as result of settings::status() at the end of the record.

J.Hilk

I believe you've been let a stray, this code is taken from my working application:

QString appDataPath = QStandardPaths::writableLocation(QStandardPaths::AppDataLocation) +QString("/");

QString settingsPath = appDataPath + QString("data/Settings.ini");

//And used this way
auto settings = new QSettings(settingsPath(), QSettings::IniFormat);

this results in a directory path

qDebug() << Q_FUNC_INFO << settings->fileName();

"/Users/jonashilk/Library/Application Support/CompanyName/Applicationname/data/Settings.ini"

artwaw

@Francky033 I don't have idea what's happening in your system. I'd try to debug the problem by hardcoding known path to the file though, like /Users/[username]/settings.ini or something.

Francky033

Hello everyone and thanks for your help!

I finally discovered the problem: I had to put a settings.sync() before the settings.status();

While the sync function doesn't seem to have any effect under Windows, Android and linux, it seems necessary to use it under macOS.

The documentation is a bit vague on this: "This function is called automatically from QSettings's destructor and by the event loop at regular intervals, so you normally don't need to call it yourself."

My problem is solved and I hope this can give a clue to people in the same situation as me. Thanks to the Qt forum and its members!

Francky033

Hello,

I am again confronted with the same problem. Everything was working fine and the next day, no directory was accessible for saving using this piece of code!
When the save box opens, I noticed that all the elements in the directory (including .ini files) are grayed out...
What I don't understand is the extremely capricious result of this function (which is so simple). One day it works, the next day it doesn't...

Is it a bug in Qt?

Have a nice day!

Francky033

SGaist

Did you restart a build from scratch ?
Re-run macdeployqt on your app bundle ?

Apple has introduced several security feature with regard to accessing the user environnement which might trigger here.