Thanks again for your reply on my post and for the extra details on your experiecne with your own extension in beta testing. It's really good to know from someone's actual, hands on experience how things are working in non-development context.

Thanks so much for the reply. I saw the the post you linked. It's actually the stackoverlow link in my original post, which I should have changed to a plain URL like you did =) One of the things I'm concerned about is all of the errors getting reported through the console. I've seen posts where otheres are confused about errors as well, but I'm not finding any answers for what they are actually telling the developer. Are you seeing a ton of error messages when Safari closes too?It is really good to know that the background process doesn't close so quickly in production. Hopefully it won't be a problem for what we're trying to accomplish.

Were you able to get a solution for this issue @adomasven? I believe I'm running into something similar where Safari closes after about 30 seconds of running the extension. For development, there definitely needs to be some sort of flag we can set to force the Safari instance to stay open. For production, we would need some way to listen for the extension being closed so we could reinstantiate it if needed. Like the OP said, we don't know how long the delay will be for a user interacting with the code in the extension, and if it's closed, there's no way to rerun it, so far as I know.Does anyone have any information on how to keep the extension running? Is there any events we can tie into in order to hear when it closes and then respond accordingly? If so, how do we go about reinstantiating the exension if it's closed?