-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
Enforce auto-push settings coming from the project file #5060
Conversation
🎉 Ta-daaa, freshly created APKs are available for 48ef709: arm64-android |
a5f1e82
to
e128ba2
Compare
@suricactus , review addressed, thanks! |
const bool forceAutoPush = mProject->readBoolEntry( QStringLiteral( "qfieldsync" ), QStringLiteral( "forceAutoPush" ), false ); | ||
if ( forceAutoPush ) | ||
{ | ||
qDebug() << "IN!!!"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the qDebug()
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, did not test myself.
81d8ca2
to
48ef709
Compare
This PR ties in with the following qfieldsync improvement: opengisch/qfieldsync#566
QField will now read and respect the auto-push settings defined in a project file, insuring that people managing a 'fleet' of QField users can easily deploy auto push to their users and insure it's turned on.