Known Issues

This article documents known issues and limitations in gettickr.app, along with workarounds where available. Understanding these issues helps you work around them and set appropriate expectations for timer behavior in various contexts.

Browser Source Refresh Issues

Some streaming software configurations experience issues where browser sources containing timers don't refresh properly after scene changes or when returning from other scenes. The timer may appear frozen or not update correctly when the scene becomes active again.

If you must stop and restart browser sources, refreshing the source after reactivation typically resolves frozen timer displays.

Mobile Browser Autoplay Restrictions

On some mobile browsers, timers with certain animation effects may not start automatically due to browser autoplay policies. These policies prevent content from playing without user interaction, which can affect animated timer elements.

If you encounter this on mobile, tapping the timer typically allows animations to start. For mobile-specific timer use, consider designs with minimal animation dependencies to avoid autoplay restriction issues.

State Synchronization Delays

Premium

Premium timer remote control isn't instantaneous due to network latency and synchronization intervals. When you pause or reset a timer remotely, viewing instances update within several seconds rather than immediately. For most use cases this delay is imperceptible, but it can matter in timing-critical scenarios.

Browser Extension Interference

Some browser extensions, particularly ad blockers, privacy tools, or content filters, may interfere with timer loading or functionality. These extensions sometimes block iFrame content or external resources, preventing timers from displaying correctly.

If timers don't appear or function properly, try disabling browser extensions temporarily to determine if they're causing the issue. You can then whitelist gettickr.app in the problematic extension's settings to allow timers while keeping the extension active for other sites.

Streaming Software Browser Source Limitations

Different streaming software platforms use different browser engines for their browser sources, and some have limitations or quirks. Certain older streaming software versions may use outdated browser engines that don't support modern web features timers rely on.

Keeping streaming software updated to recent versions typically resolves these compatibility issues. If you're using older software versions and experience problems, updating is the recommended solution. Most modern streaming software versions support timers without issues.

WordPress VIP and Enterprise Restrictions

Some WordPress VIP or enterprise hosting configurations have strict security policies that filter or block custom HTML including iFrames. This isn't a gettickr.app limitation but a hosting environment restriction designed to prevent potential security issues.

If you're on a restricted WordPress environment and can't embed timers despite following the integration guide, contact your hosting provider or WordPress administrator about allowing iFrame content from gettickr.app specifically. They may be able to whitelist the domain while maintaining overall security policies.

Safari Private Browsing Limitations

Safari's private browsing mode has restrictions on local storage and some web APIs that can affect timer functionality, particularly for features that rely on browser storage. While basic timer countdown functionality typically works, some advanced features may not function fully in Safari private mode.

Using Safari in regular browsing mode rather than private mode resolves these limitations. This is a general Safari private browsing restriction affecting many websites, not specific to gettickr.app.

Long Duration Countdown Accuracy

Timers running for extremely long durations measured in weeks or months maintain accuracy, but edge cases can occur with device sleep states or hibernation. If a device running a timer goes into deep sleep or hibernation, the timer may not update until the device wakes.

For very long countdown applications, periodically checking that timers are running correctly ensures continued operation. When devices wake from sleep, timers recalculate their current state and should show the correct countdown, though there may be a brief moment while they reinitialize.

Multi-Monitor Streaming Setups

Some users report issues with browser sources on secondary monitors in multi-monitor streaming setups, particularly with certain graphics card configurations. The timer may not render properly or update inconsistently when the browser source is on a secondary display.

If you encounter this, try moving the browser source to your primary monitor in the streaming software scene. You can still position it anywhere in your stream output; the issue relates to which physical monitor the software renders the source on, not where it appears in your stream.

Third-Party Platform Changes

When gettickr.app integrates with third-party platforms like streaming software or website builders, changes to those platforms can occasionally affect timer integration. An update to OBS Studio, WordPress, or other platforms might change how they handle browser sources or iFrames.

These issues are typically temporary and resolved through updates to either the platform or gettickr.app to restore compatibility. Checking the help documentation and support channels when platform updates occur can provide guidance if integration issues arise.

Browser Cache Staleness

Occasionally, browsers cache older versions of timer code or assets, causing timers to not reflect recent updates or fixes. This results in unexpected behavior that doesn't match current timer capabilities.

For embedded timers that viewers access, most browsers automatically request fresh content periodically, so cache staleness is usually temporary and self-resolving.

Reporting New Issues

If you encounter issues not listed here, please report them through the support portal. Detailed information about your setup, what you were trying to accomplish, and any error messages helps diagnose and resolve issues quickly. User reports of new issues help improve gettickr.app for everyone.

While these known issues exist, they affect relatively few users and workarounds are generally available. Most users experience reliable timer operation without encountering any of these limitations. Understanding them helps you troubleshoot effectively if you do encounter problems and ensures you can work around them when necessary.