Hotfix

Update 38: Warframe: 1999

mobile
Warframe: 1999: Hotfix #8
Jan 22, 2025

We’ve deployed an iOS update that resolves launcher crashes, UI fixes, and more. While we are calling this a hotfix, it is actually a small CERT update (learn more about what that means here).

Depending on your Automatic App Update preferences, you may need to manually update the app.

Fixes

  • Fixed a rare crash occurring upon launching Warframe on iOS 15 & iOS 16.
  • Fixed being unable to confirm Relic selection in the Trading window using touch controls.
  • Fixed the Komi boards within Duviri having no functionality on iOS.
    • Previously, players would be able to initiate the Komi game but could not interact with it, forcing them to quit and relaunch the app. Now, Komi is playable on iOS.
  • Fixed the Map, Chat, and Escape buttons during Bounties being too small in size and having improper placement.
  • Fixed a loss of touch control UI after Host migration in Höllvania missions. Fixed iPhone 16 players’ Graphics Quality Preset defaulting to Low.
    • Upon install, iPhone 16 players should have the Graphics Quality Preset on High by default (with the option to switch to Medium, Low, or Custom).
  • Fixed the Sensor Ring appearing in cinematics during Angels of the Zariman and The Hex Quests.
  • Fixed the Backroom’s mirror having no reflection.
  • Fixed being able to use Warframe Abilities during a sequence in The Second Dream Quest where they are intended to be disabled.
  • Fixed the Operator touch controls appearing on screen when unintended during a sequence in The New War Quest.
  • Fixed being unable to access the Gear Wheel in the second half of The Hex Quest when playing with touch controls.
  • Fixed being unable to exit out of Albrecht’s Requiem rune murals when playing with touch controls.
  • Fixed the missing Heat Meter UI during the second phase of the Exploiter Orb fight.

Changes

  • Added Autofire will now target the Scaldra Harbingers in the H-09 Apex Tank battle.
  • Changed the invisible Send Error Log button to require a double tap to initiate.
    • This change is intended to prevent accidental usage when the invisible button is close to other on-screen prompts.
    • For more information on how to share error logs, including the invisible button, click here.