Skip to content
Brand Logo

tetrify Community
  1. Home
  2. Bug Reports
  3. Fixed Bugs

Fixed Bugs

Bugs which have been fixed thanks to your reports!

This category can be followed from the open social web via the handle [email protected]

8 Topics 26 Posts
  • T

    Search no longer works

    Moved fixed 2.5.1
    4
    0 Votes
    4 Posts
    72 Views
    T
    Great, it now works! Thank you very much!
  • L

    Issue with Arabic Text Display After Latest Update

    Moved fixed 2.4.1
    3
    0 Votes
    3 Posts
    73 Views
    gagikG
    Fix has been deployed, it'll be available as part of the next update pending App Store approval, should take at most 24 hours.
  • A

    Routine start date issue

    Moved fixed
    4
    0 Votes
    4 Posts
    130 Views
    gagikG
    This is now fixed in 2.4.0!
  • T

    Can’t see what I type on iPad

    Moved fixed 2.3.9
    6
    0 Votes
    6 Posts
    145 Views
    gagikG
    Glad to hear! Going to mark this as fixed
  • gagikG

    Authentication issues

    Moved fixed
    2
    0 Votes
    2 Posts
    75 Views
    gagikG
    Authentication issues have been resolved! We have been experiencing a great rise in bot traffic recently so this was our anti-bot protection acting too aggressively against our own login mechanism... But the good news is that logins should be restored now! No updates needed.
  • S

    Routines Loop

    Moved fixed 2.3.8
    3
    1 Votes
    3 Posts
    104 Views
    gagikG
    The 2.3.10 update has been released, it may take an hour for it to reach every App Store! Once 2.3.10 update is available to you, please update your app through the App Store and let me know if it works now. https://apps.apple.com/us/app/tetrify-text-yourself-notes/id6447967703?l=da
  • communityC

    Double Routine Message

    Locked Moved 2.3.7 fixed
    2
    0 Votes
    2 Posts
    150 Views
    gagikG
    This has been fixed now
  • communityC

    Notifications are not being enabled for new users

    Locked Moved 2.3.6 fixed
    2
    0 Votes
    2 Posts
    140 Views
    gagikG
    Now with 2.3.6, this has been fixed