Commit dd40bd27 authored by Volker Krause's avatar Volker Krause
Browse files

Don't use GenericDataLocation on Android

That's the regular file system outside of the app bundle, which needs
extra permissions to write to.
parent e14b75c7
Pipeline #163116 passed with stages
in 3 minutes and 18 seconds
......@@ -16,7 +16,12 @@ using namespace KPublicTransport;
static QString basePath()
{
return QStandardPaths::writableLocation(QStandardPaths::GenericDataLocation) + QLatin1String("/org.kde.kpublictransport/location-history/");
#ifdef Q_OS_ANDROID
constexpr auto dataLoc = QStandardPaths::AppDataLocation;
#else
constexpr auto dataLoc = QStandardPaths::GenericDataLocation;
#endif
return QStandardPaths::writableLocation(dataLoc) + QLatin1String("/org.kde.kpublictransport/location-history/");
}
LocationHistoryModel::LocationHistoryModel(QObject *parent)
......
  • What's the use case for not using AppDataLocation always? Sharing recent locations between apps?

  • Yes, exactly. The idea is to allow for the same recent/favorite locations in e.g. KTrip and Itinerary.

Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment