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
Currently, register_device can be executed repeatedly resulting in all the device slots being assigned. Although this may sound like an edge case, in our organisation we have a lot of users in multiple countries and if we adapted register_device we risk running out of device slots almost immediately. As a workaround, we've had someone manage this manually which is far from ideal 🤯
I propose adding a device limit per user functionality to mitigate this risk. This can be achieved by adding a new Fastlane environment variable e.g. DEVICE_REGISTRATION_PER_USER_LIMIT and adding a new parameter, device_owner_email to register_device. In theory, when register_device is executed, it will check if a device has been registered with the same device_owner_email, if it has and the DEVICE_REGISTRATION_PER_USER_LIMIT has not been exceeded then it will continue to register the device. The device_owner_email list can be stored inside a file in the profiles repository which will be updated as a result of adding the device.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently,
register_device
can be executed repeatedly resulting in all the device slots being assigned. Although this may sound like an edge case, in our organisation we have a lot of users in multiple countries and if we adaptedregister_device
we risk running out of device slots almost immediately. As a workaround, we've had someone manage this manually which is far from ideal 🤯I propose adding a device limit per user functionality to mitigate this risk. This can be achieved by adding a new Fastlane environment variable e.g.
DEVICE_REGISTRATION_PER_USER_LIMIT
and adding a new parameter,device_owner_email
toregister_device
. In theory, whenregister_device
is executed, it will check if a device has been registered with the samedevice_owner_email
, if it has and theDEVICE_REGISTRATION_PER_USER_LIMIT
has not been exceeded then it will continue to register the device. Thedevice_owner_email
list can be stored inside a file in the profiles repository which will be updated as a result of adding the device.Beta Was this translation helpful? Give feedback.
All reactions