Closed tinashe404 closed 2 years ago
@tinashe404 I took care of this at API level, please check and share your feedback
@athandle It's working on the dev environment. I'm assuming you haven't pushed it out to prod yet? @Shava
still says it's invalid.
@tinashe404 deployed to prod just now
@athandle This is working as expected. @Shava
has successfully update and is up and running. I also checked regular atsign activation and this is still working fine.
Describe the bug There are some atsigns that people got before we stopped allowing them to enter capital letters into the atsign generator. While looking into something, I found that I am not able to activate
@Shava
.To Reproduce Steps to reproduce the behavior:
Expected behavior All atsigns should activate the same.
Video https://user-images.githubusercontent.com/69275762/153429617-2b6eb6b1-7f2b-4064-a9f4-5cafdc8f70ee.MP4
Were you using an @application when the bug was found?