The only possibility here is that your phone comes with some sort of 
feature to delete data of an app that you haven't "used" for a while, 
and for some reason it has determined that Shelter wasn't "used". This 
feature is even available on stock Android but normally it shouldn't be 
triggered for Shelter as long as _some_ apps inside Shelter are used 
semi-regularly. You can disable it in Settings -> Applications (find 
Shelter there), but really it should not happen for Shelter.

Unfortunately there's no way for Shelter itself to check whether this 
option is enabled and prompt the user to disable it.

On 9/1/24 6:19 AM, Benjamin wrote:
> Hello,
> 

I do not even use Play Services myself and I have never encountered any 
issue with Shelter (otherwise I would have fixed it long ago). I have 
not been running Play Services myself for at least 4 years.

Again, your error only happened after Shelter jumped to the system setup 
UI. I do not know what Insular is doing different here, but there really 
is only one way to trigger that UI...

On 3/23/24 11:50, Skibididoo wrote:
> Update:
> 
> Shelter is somehow dependent on Google Play Services
> 
> 

Unfortunately, I don't think logcat would really help a lot here. 
Android's work profile setup process is not known to be super verbose in 
logs, and your failure happened in Android's work profile setup flow, 
not in Shelter, so there is not really anything visible from Shelter at 
that point.

You could try to send a logcat taken right after that error happens 
privately (not to the mailing list due to privacy concerns), but I can't 
guarantee to be able to find anything in there.

On 3/23/24 10:22, Skibididoo wrote:
> Thanks for the reply! Shelter was the first work profile app I had
> tried. I tried Insular as a troubeshooting step to check if something
> was wrong with the work profile setup.

Usually this failure mode happens because there is already another work 
profile created by another application. If you have tried Insular 
**before** Shelter, then it might simply be caused by Insular's work 
profile not being **completely removed** before you installed Shelter. 
Insular would still work because the work profile was also owned by 
Insular before, so the system would simply recreate the work profile for 
it. But if you try to override an Insular work profile with Shelter's, 
it would fail with that "Contact your IT admin for help" dialog.

I would suggest trying to **completely remove** all traces of Insular 
from your system before trying Shelter. This includes going to Settings 
-> Accounts and removing the entire preexisting Work Profile. If this 
doesn't work, then unfortunately I cannot think of another reason why 
Shelter would fail at the very first step. The setup process should be

Usually this failure mode happens because there is already another work 
profile created by another application. If you have tried Insular 
**before** Shelter, then it might simply be caused by Insular's work 
profile not being **completely removed** before you installed Shelter. 
Insular would still work because the work profile was also owned by 
Insular before, so the system would simply recreate the work profile for 
it. But if you try to override an Insular work profile with Shelter's, 
it would fail with that "Contact your IT admin for help" dialog.

I would suggest trying to **completely remove** all traces of Insular 
from your system before trying Shelter. This includes going to Settings 
-> Accounts and removing the entire preexisting Work Profile. If this 
doesn't work, then unfortunately I cannot think of another reason why 
Shelter would fail at the very first step. The setup process should be

This is not a Shelter problem. Cross-profile app linking in Android 
means one thing specific, and that is to allow some apps specifically 
designed to support cross-profile data sharing such as input methods to 
work. Opening links is part of this (although Shelter already allows 
ACTION_VIEW to cross profiles, so not sure why Tiktok doesn't work in 
this case. I suspect it is due to Android's permission checks for link 
openers)

On 3/16/24 21:23, Samuele Verga wrote:
> I feel like it should work tho, a simple use case can be having TikTok 
> installed on shelter and opening TikTok links from the main profile, the 
> current behavior doesn't allow this but allows file sharing.

Hi Roland,

The translation page should be unlocked now.

Regards,
Peter.

On 2/25/24 03:15, Roland Kim wrote:
> Greetings.
> 
> I've discovered that the Weblate interface has been locked for any further translation submissions or updates with the message below. Mind taking a look of this?
> 
>> The translation is temporarily closed for contributions due to maintenance, please come back later.
>> The translation was automatically locked due to following alerts: Could not update the repository.

The best I can say about this is that I cannot reproduce this issue on 
any of my pure AOSP builds. Maybe it is an AOSP bug triggered by some 
specific config overlay option, but I would have no way to tell unless 
we know how to reproduce.

On 2/21/24 09:38, L wrote:
> What I was trying to say is that for some reason, browsers in a Shelter 
> work profile are treated by system as needing that permission.
> 
> I am a developer and I know that access to keyboard normally should not 
> dependent on interact across users permission.
> 
> My rom has AOSP (vanilla) implementation of work profiles and neither 
> DevicePolicyManager nor policy itself has been modified.

INTERACT_ACROSS_USERS is never supposed to be had by normal 
applications. Accessing clipboard should never require this permission. 
This is a bug of your operating system, not something Shelter can 
address or work around.

On 2/21/24 03:01, L wrote:
> This bug is confirmed. No browser is functional. Any touch of clipboard 
> area results in immediate crash with logcat entry: permission 'interact 
> across users or full is required. The same browser in personal profile 
> works fine. For some browsers in work profile are required to have these 
> permissions.
> 
> Bug present in Firefox, Fennec, Iceraven, Kiwi and any other that was tried.

I don't see what's originally quoted here but connected apps is now a 
thing in the latest Shelter release.

On 2/6/24 07:34, Elijah Lang wrote:
> Hey Peter, love this app and all the great work you do. Has this feature 
> been implemented since Android 14 came out? I've been hoping to see this 
> for the past few years.
> 
>> Thank you. Eventually I'll add both of these features -- hopefully before A14 is actually released.