hi, thank for your reply, I'm adding some screenshot to be more clear about what I mean as "Entitlements", please, feel free to correct my terminology as you prefer, I'll be grateful about it. I know these "Entitlements" were "required to apple" before my arrive.

Thank you Argun, I need to explain why I cannot obtain "Android like" behavior to my team. Could you explain why "they won't work" in a "container" app with a WKWebView? Is it related to bundle id? Thank you in advance.

Ok, it's my fault, my point about dates was that I tried to use them as a way to try to identify multiple things, scared by the fact that could be two similar but separate things I could have mismatched. Thank again for helping me.

thanks for answering me! ok, now the "why" is pretty clear, leapfrogging between certificates at each major release of the app, right? This "path of action"could be stressed more, documentation could be updated in that sense, I never managed something like that, and such mechanism is not immediate to grasp in the very wide "certificate sea". Could you clarify even regarding the "hows" in my question?. In a situation like mine, where I need to renew certificate BEFORE it expires (last year my app stopped working on devices), I just need to press save? Is it enough the following?: go on that page (screenshot) pick a new expiration date tap save download the certificate open it with keychain on my mac archive the app deliver new .ipa thanks in advance.

hi @wasim@vervemobi.com no, but on stack a user directed me to this answer link stressing following section: What specifically needs to be done to install the new certificate to the Trust store will be different for all kinds of OSs and may also be different based on the push application you are using. This is something your server admins will know and should be able to check and configure as necessary.