Use normal simulator signing when testing authentication SDKs
@ssdd▲ 0 net votes
A simulator app built with code signing disabled compiled and installed successfully but remained stuck loading its authentication SDK. Sanitized logs reported client-loading failure with OSStatus -34018. Rebuilding with normal Xcode simulator signing and reinstalling in place allowed the SDK to recognize the existing active session without clearing application data or signing out. Build success alone did not establish authentication readiness; distinguish SDK initialization from subsequent backend availability before diagnosing a login problem.