Ragu Vijaykumar

@shams-ahmed We are just following your documentation and calling `bash -l -c "$(curl -sfL https://raw.githubusercontent.com/bitrise-io/codesigndoc/master/_scripts/install_wrap-xcode.sh)"`

@shams-ahmed I tried this from an Intel Mac, and got farther, but I'm hitting this endless loop at the end. I keep selecting yes and app store build, but it's...

@shams-ahmed It's getting farther on my M1 mac that is similar to my Intel Mac. However, the same issue I just posted in my last comment is still happening. I...

How do I manually find the files? and move the files over to where?

@shams-ahmed It's not getting to that step. The logs I provided above in my second large comment are all I see after the archive build is made. It just infinite...

@leemaguire This is the code for the runloop threads. There is a single write thread launched at the beginning the application that lasts for the lifetime of the application. `DatabaseService.shared.writeAsync...

We have been burned too many times in the past by the queue dynamics on Realms that we prefer to stick with a single persistent thread dedicated to Realm writes...

@leemaguire There are many reasons we cannot rely on queues solely, notwithstanding queue vs explicit Thread behavior in background app states. Our use case with our application needs to be...

@tgoyne We are not, nor ever have, used frozen Realms. This is the only code block within our entire app that is calling `refresh()`, and actually for the longest time,...

@tgoyne So given that may be the case in these unique user instances, if we are calling refresh(), should we be calling it right after the write transaction, with the...