What to check first
Choose a test account that owns no gems. Keep the browser session open and have somewhere secure to save the recovery codes RubyGems.org shows after enrollment.
KeySigner setups
- Test a RubyGems sign-in code →KeySigner on iPhone or Mac with Sign-in codes
What it covers
This test covers browser sign-in. Release commands and trusted publishing have their own authentication requirements.
Troubleshooting
Does the test account reject your enrollment code?
Confirm the KeySigner entry belongs to that account and try a new code before it expires. If RubyGems.org expired the enrollment QR code, start registration again with the new QR code.
Two-factor codes for PyPI, RubyGems and Docker Hub →
Check RubyGems status for reports on the RubyGems.org package registry.
Documentation and support
RubyGems documentation
Register an authenticator on RubyGems.org
Use a recovery code
Set up trusted publishing for a gem