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]

9 Topics 30 Posts
  • 0

    Cannot export

    Moved
    4
    4 Posts
    203 Views
    gagikG
    This has been fixed in the latest version!
  • 0

    Search no longer works

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

    Issue with Arabic Text Display After Latest Update

    Moved fixed 2.4.1
    3
    3 Posts
    142 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.
  • 0

    Routine start date issue

    Moved fixed
    4
    4 Posts
    211 Views
    gagikG
    This is now fixed in 2.4.0!
  • 0

    Can’t see what I type on iPad

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

    Authentication issues

    Moved fixed
    2
    2 Posts
    157 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.
  • 1

    Routines Loop

    Moved fixed 2.3.8
    3
    3 Posts
    212 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
  • 0

    Double Routine Message

    Locked Moved 2.3.7 fixed
    2
    2 Posts
    251 Views
    gagikG
    This has been fixed now
  • 0

    Notifications are not being enabled for new users

    Locked Moved 2.3.6 fixed
    2
    2 Posts
    272 Views
    gagikG
    Now with 2.3.6, this has been fixed