You probably had the Shelter version signed by me (and not F-Droid) 
installed, and that is likely why you cannot re-install Shelter 
properly. Try the version from my own F-Droid repository 
(https://fdroid.typeblog.net/), and if it installs fine, you can just 
force a recreation of the work profile. You will lose all data inside 
the profile, though, and there is no way to work around that.

Regards,
Peter.

On 9/9/23 05:59, Marc Haber wrote:
> Hi,
> 
> I use Shelter to keep WhatsApp from reading my main contacts lists.

No, it is outside of the scope of Shelter to implement features not 
available to a profile owner. I don't see why there is a problem in 
using another app to achieve something completely different.

On 5/28/23 11:22, Rahatul Ghazi wrote:
> So, do you think you'll utilize shizuku like Hail does? It can disable, hide and suspend apps with shizuku.
> 
> Currently, I need the work profile but I also need to freeze apps in the main profile. Can you give me a solution to this, please? Thank you.

Device Owner and Work Profiles are incompatible with each other, because 
Work Profiles are supposed to deprecate the Device Owner feature in its 
entirety. That is what I mean by saying the Device Owner feature will be 
removed in a future Android release, and also why Shelter does not and 
will not support being a Device Owner.

On 5/28/23 10:56, Rahatul Ghazi wrote:
> So, I wanted to freeze my main profile apps too. I'm using Hail but I felt like I was using too many apps for same function. I thought shelter could do it.
> 
> Anyway, How can I set other apps as device owner, while keeping shelter as work profile owner? Because it doesn't let me set Hail as device owner when Shelter is the work profile owner.

It's not a supported use case of Shelter -- and Device Owner is a 
deprecated feature in Android anyway and will be removed in a future 
version.

On 5/28/23 08:40, Rahatul Ghazi wrote:
> Hi Peter.
> 
> I want to freeze my main profile's apps with shelter. How do I do that?

Hmm, I actually just assumed that this would never work in a work 
profile -- I didn't know all you need is just a stub. It is definitely a 
great idea but I will likely need to find a contactless payment app to 
test with, and unfortunately in where I live the only option seems to be 
Google Pay, but that won't work if only installed in a work profile (not 
that it would accept my bootloader-unlocked device, either).

On 5/27/23 12:13, Victor Bessonov wrote:
> Hey! Wanted to ask for a bit uncommon feature (feels a bit like
> workaround either for a bug or for a "design decision")
> I want to isolate my banking apps just like any other "big brother"
> apps inside work profile managed by Shelter, however there may be a
> problem - at least in my LOS20-based iodeOS when I try to open
> "Contactless payments" setting (Connected devices->Connection

Thank you. Eventually I'll add both of these features -- hopefully 
before A14 is actually released.

On 5/18/23 13:00, Victor Bessonov wrote:
> Got really excited about this - wanted to add cross profile
> interaction for Android Auto.
> First of all, it looks like setCrossProfileCalendarPackages with null
> argument gives unlimited app access only to cross-profile Calendar
> APIs and according to the docs it will be deprecated in A14.
> But there is a setCrossProfilePackages method which seems to give full
> cross-profile access, however it accepts only arguments with type
> Set<String> reflecting packagenames of apps allowed to make such a
> request and null as a wildcard for all is not allowed.
> 

Sorry, I have not implemented the new settings yet due to a bunch of 
things happening in my life right now. I'll try to remember to get back 
to it some time soon -- which I think shouldn't be too far away...

In the mean time, if you are willing to take a shot at this, I am always 
open to a pull request / patches via email.

Regards,
Peter.

On 3/12/23 16:16, Elijah T. Lang wrote:
> Hey Peter, we appreciate how much work you do for Shelter! So I hate to 
> ask this, but would it be feasible to release an update soon, even if 
> the only change is to allow Connected Apps? Just having this one setting 

Hi,

Unfortunately Shelter itself cannot do anything about this type of bugs. 
It's either something that has to be handled by the screen recording app 
itself, or it is a bug of AOSP (or GrapheneOS downstream, but it's less 
likely). Sadly there is not much I could do here.

Regards,
Peter.

On 2/24/23 05:08, vep_quieras@simplelogin.com wrote:
> Hi Peter,
> 
> I'm experiencing an issue with screen recording apps within the work profile. I'm able to record the app's display, but not its sound, despite enabling the "record audio" option with "device audio" selected. I've tested this with multiple apps, but no sound was ever saved within the recording. The only type of sound it can record seems to only be input from the microphone when it's selected.

Hi,

I believe Google Family Link acts as the Device Manager app for your 
kid's device(s). In that case, I do not think Google would expose an 
option to allow the use of other device admin / work profile managers, 
because that is not an expected use case.

Regards,
Peter.

On 2/18/23 14:28, Michael Hoffmann wrote:
> Hello,
> 
> I love Shelter and want to set this up for my kids too. On their 

We make no use of proprietary Samsung knox APIs, so any bug related to knox can only be caused by them breaking compatibility with upstream AOSP APIs. Please contact Samsung for any potential breakage resulting from their proprietary solution.

Regards,
Peter.

On 12/18/22 10:03 AM, Robert Link <rlink@gmx.de> wrote:
> Dear Peter,
> 
> I came across a potential issue on the latest update of Samsung Knox to 
> 3.9.
> 
> Since I ran that update, Whatsapp starts and works after
> a fresh installation from Shelter into the Work profile;
> but after some time it doesn't restart and only ends in error