Firebase Phone Auth fails with "no matching SHA-256 registered" despite correct SHA-256 registered in Firebase Console (Play App Signing key)
SHA-256 mismatch causes Firebase Phone Auth failures on Android, affecting auth integration.
Steady32
signal score
as of 2d ago
🔗 3
sources · android
↑ Accelerating
7-day est. ~51
Why this scored 32
every term, weightedEngagement gained per hour since the last capture, against the fastest item on its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities are talking about the same entity
Decays to zero over 14 days
Subtracted once something is big and old — we rank what's next, not what's peaked
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Outlook
low confidence · estimate, not a guarantee7-day
~51
range 14–63
14-day
~56
range 17–71
30-day
~58
range 14–78
Signal history
7-day window (free)— — projected trajectory (estimate, not a guarantee)
Entities
Embed a live signal badge
[](https://www.signalcrest.app/topic/so%3A79996011)
Drop this in a README or blog post — it updates automatically as the score moves.