Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
2.1.6
3.0.6
Issue ID
TMPB-57
Regression
No
[Mobile][TMP] Link tag stops working after the first time when the link switches to another app
Reproduction steps:
1. Open attached Project "Case_1333424"
2. Build and Deploy the Project to a mobile device
3. Click the text in the Build "my link"
4. After the browser opens switch back to the App
5. Try to click the text again
Expected result: Browser opens again
Actual result: Browser does not open
Reproducible with: TMP 1.5.6 (2018.4.34f1), 2.1.6 (2019.4.26f1), 3.0.6 (2020.3.7f1, 2021.1.6f1, 2021.2.0a16)
Reproduced with:
iPhone 6 (iOS 12.4.8)
iPhone 7 (iOS 12.3.1)
iPhone 12 Mini (iOS 14.1)
VLNQA00286, Meizu - (PRO 5), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00317, Vivo V1924A (V1924A), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
VLNQA00294, Oppo Reno Z 中国版 (PCDM10), Android 9, CPU: Mediatek MT6779 Helio P90, GPU: PowerVR Rogue GM9446
Notes:
- After returning to the App, the link starts working very inconsistently: almost always it just does not work, however, sometimes it still fires
Comments (1)
-
ashishswain_paperboat
May 05, 2021 10:03
This can be fixed by resetting the m_selectedLink to -1 in TMP_TextEventHandler class
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.