You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If it is greater, skip the logic defined in check_signin function and also print a user-friendly message to sign in via the Mac App Store GUI. Unfortunately, for the time being, this is the workaround mentioned in the issues.
defcheck_signin(self):
''' Verifies that the user is signed in to the Mac App Store '''# Only check this once per executionifself._checked_signin:
returnifself.is_version_greater(self._mac_version, WORKING_MAC_VERSION_MAS_ACCOUNT):
print('WARNING: You must be signed in via the Mac App Store GUI else error will occur')
else:
rc, out, err=self.run(['account'])
ifout.split("\n", 1)[0].rstrip() =='Not signed in':
self.module.fail_json(msg='You must be signed in to the Mac App Store')
self._checked_signin=True
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
justinpjose
changed the title
general.community.mas - remove signed-in check from Mac OS 10.12+
general.community.mas - remove signed-in check from Mac OS 12.0+
May 12, 2023
Context
Unfortunately, as of Mac 12.0 and onwards, the
mas account
command isn't functioning correctly.Issues have been already raised regarding this:
mas-cli/mas#417
Problem
The
mas account
is used as a check to see if the user is signed in before installing or upgrading an app using mas via Ansible.As of Mac 12.0 and onwards, we cannot install or upgrade an app via mas via Ansible
Solution
Detailed in the
Additional Information
sectionIssue Type
Feature Idea
Component Name
mas
Additional Information
Solution
In the
check_signin
function,community.general/plugins/modules/mas.py
Line 157 in f833982
We should do the following:
check_signin
function and also print a user-friendly message to sign in via the Mac App Store GUI. Unfortunately, for the time being, this is the workaround mentioned in the issues.Code of Conduct
The text was updated successfully, but these errors were encountered: