Fallout Shelter bugs



This page describes Fallout Shelter bugs.

Android

 * Crippling performance issues and performance leaks with any action. Lag spikes can become unbearable after less than 10 minutes of heavy activity, so bad as to even make quitting the game difficult.
 * To fix this issue, open the game options and set CAM SENS to 0% and Turn-Off HD ZOOM OUT.
 * The game crashes when heavily using the room assignment list. Often the game will crash when using the room assignment list to assign dwellers to rooms.
 * Sometimes deselecting a room or a dweller will not change the interface, the interface will remain until you select and deselect another dweller or room.
 * After the tutorial where you build the power plant, it tells you to select a dweller to assign to the power plant but the dweller may not be selectable.
 * Sending out an explorer sometimes results in an absurdly large return time when recalled.
 * During raider attacks if the game crashes, the game may become locked in the "under attack" mode. There will no longer be raiders, but dwellers will still be in attack mode, and absolutely no resources will be produced, even in rooms that weren't attacked.
 * A possible fix is quitting and re-entering the game through the main menu.
 * When you unequip armor and weaponry from a dweller before they enter the vault the game will crash and, while restarting it crashes when trying to load the vault,
 * When in the loading screen after choosing a vault number, the game will crash and send you back to the phone's home screen.
 * The game may get stuck on the "Loading..." screen when loading the Vault.
 * The only known fix is to force stop the game then clear its cache.
 * If this doesn't work, reset the device as well.
 * Occasionally when dwellers are sent to explore, they will end up exploring for an infinite amount of time without accumulating items or experiencing events.
 * This is caused when a player advances the phone's timer ahead. After the amount of time that was jumped ahead passes, the explorers should start encountering creatures and collecting loot again.
 * The game may constantly crash upon opening the objectives screen. Restarting the game does not fix the problem.
 * Fix: reddit fix
 * Game crashes on "Please stand by" screen if the cellphone shuts down while playing previously.
 * The only known fix currently is to completely reinstall Fallout Shelter, as the crash destroys any existing saves.
 * When assigning Vault Dwellers to a new room or when two couples go to have a baby at the same time (overlapping themselves), they will occasionally become invisible and unable to be selected. To fix this close down the app completely.
 * Another fix that works sometimes is to make the invisible dweller go through an elevator by assigning him to a room on a different floor by using the assignment list menu.
 * If the phone's batteries run out after opening a lunchbox and unlocking the cards, the cards will disappear once the game has restarted.
 * In radroach incidents, sometimes the workers will animate as running around uselessly or continuing their work task instead of assisting with exterminating the radroaches if they are unarmed.
 * XP earned while the vault dwellers are exploring the wastes doesn't seem to increase their level.
 * When reviving dwellers there's a chance that an invisible corpse will remain and upset anyone working there. The only known ways to fix this so far is to delete the room and rebuild it or have another dweller die in the same room and deal with the corpse.
 * During raider attacks, dwellers from other rooms take damage although raiders are not present. The dwellers in the room where raiders are do not shoot them.
 * This seem to happen when assigning someone to an empty room raiders are about to leave. The raiders will look like they're still in that room while they are actually fighting somewhere else, explaining neither the dwellers nor raiders attacking, and dwellers in another room taking damage (and thus actually damaging the raiders).
 * Occasionally fires will not be put out, resulting in an inability to collect resources from any other room.
 * When explorers return, attempting to collect the items results in the failure to collect them despite having plenty of storage space.
 * When a selected dweller dies from an emergency, the game doesn't deselect them and it is still possible to use a stimpak on them. Despite this, the dweller will still die, maintaining a normal facial expression.
 * When switching between apps while a vault is on fire, upon returning, the fire cannot be extinguished.
 * During a radroach infestation, it is possible for the radroaches to be invincible and eventually kill all of the dwellers. This can also occur with mole rats, radscorpions and feral ghouls.
 * A solution: Move all dwellers out the that room and the adjacent rooms. They will infest other rooms, so repeat the tactic until they give up.
 * The core gameplay can be drastically altered by messing with the device's internal clock. Should one set one's clock backwards, all incidents cease unless triggered by the player, and all production rooms gain whatever amount of time that the player went back to added to their next production time. The production rooms can be reset by rushing, allowing a player to collect resources risk-free for as long as the clock has been set behind. This can also be used to manipulate the time dwellers spend in the wasteland, but they won't collect anything until the clock has been caught up. The altered time will affect their enemy spawns and loot drops, however, and can also be used to bring them home prematurely by recalling them after setting the clock back and then rolling it forward. Changing the clock or getting to the point in time the clock was changed to originally should fix this highly exploitable bug.
 * If a room is rushed immediately prior to setting the device's clock backwards in time to exploit this bug, upon having set the clock backwards, the failure rate of a rush for the room in question will have skyrocketed. This is likely because the game gauges rush failure rate based partially on the time since the last rush, and it decreases with time. Since the previous rush is read as having been in the future, the failure chance is elevated accordingly.
 * The service may be uninstalled as a possible workaround, but it renders add-ons unable to be purchased.
 * If running on a KitKat OS, use Dalvik runtime as a workaround.
 * On a rare occasion an elevator may become indestructible. While attempting to destroy it, "the elevator is in use" message shows. This happens even if there are no other rooms or elevators connected to it (apart from its parent one) and no dweller is moving between any rooms/levels.
 * Exiting and reloading the vault will normally fix this.
 * This crash is because of a mole rat objective and will stop happening if you can open the game and delete the objective before the crash happens again.
 * Occasionally time will not pass for an exploring dweller with the app closed, while leaving all other time functions, such as pregnancies, room timers, and questing unaffected.
 * When one returns to their vault after completing a quest, the Caps and Nuka-Cola Quantum counters will be maxed out for about 3 seconds.
 * If a Daily Reward becomes due while the player is online and the player chooses to collect the reward, the Happiness registered may be considered 0% regardless of your actual current Happiness, thus resulting in a smaller daily reward.

iOS

 * Upgrading a room will not work if you have the same amount of caps as the cost of upgrading. For example, if a room upgrade costs 750 caps and the player has 750 caps, the player would have to wait until they have reached at least 751 caps in order to purchase the upgrade.
 * The game will freeze up and black screen with no discernible pattern. The app can be reopened by returning to the home screen. Brief data can be lost in these instances, such as caps gained, objectives removed or completed, and rooms built. It may also result in the permanent pregnancy bug.
 * If the Vault is bigger than 20+ civilians, the vault may never load because of permanent crashes at the loading screen of the vault.
 * If the game crashes while naming or just after naming a baby dweller, The mother may remain pregnant and not leave the pregnant state after rebooting. Another possible cause appears to be deleting or modifying the residence in which the dweller got pregnant, after they've gotten pregnant, although this is not true in all cases.
 * During a radroach infestation, it is possible for the radroaches to be invincible and eventually kill all of the dwellers.
 * It is possible for Fallout Shelter to crash when a rush is attempted.
 * If a dweller is equipped with RadAway and stimpaks and is on their way to the wasteland, but the expedition is canceled by an event such as rad roach infestation, fire, or raider attack, the items equipped to the dweller will be lost.
 * When reviving dwellers there's a chance that an invisible corpse will remain and upset anyone working there. Also removing a corpse during an incident may create a ghost. The only known way to fix this so far is to delete the room and rebuild it.
 * After sheltering a random survivor, they may keep their original outfit instead of changing to a vault jumpsuit. This can be verified when going to change their outfit, the name of the clothing is a modifier with an number at the end, example: Casual01.
 * Dwellers sent to explore the Wasteland will sometimes change their outfit if they find an outfit that is the same rarity as the one currently equipped. The original outfit will be moved to their inventory.
 * Dwellers may become invisible. It is unknown what causes this, but closing the game and reloading it restores their visibility.

PC

 * Version 1.13.13 Cannot click on the Build Hammer or the menu icons in the lower right hand corner.
 * Removing a weapon, outfit or pet on a dweller after they get sent to the wasteland (done by clicking on the dweller in walking state) deletes said item.