Known Issues 7/26/2018

CG_SBCrumb
685 posts EA Community Manager
KNOWN ISSUES
7/26/2018



iOS Sith Fighter Bundle Pricing
iOS store has a wrong price ($30.99 instead of $29.99) We will be crediting all players who purchased this bundle 200 crystals if they purchased at the incorrect price. The price has been updated on the store and crystals will be credited later today.

Sith Fighter Marquee Event
Reinforcement slots are being determined by the player’s capital ships and not the event version. We will monitor if this is causing too many players to be unable to complete the Marquee and fix this issue in the future.

Mod Secondaries Server Update Issues
We are fixing incorrectly adjusted Mods due to last week’s server fix. We will be rolling back affected mods to what they were prior to the server update. You can find more details in our post here

Territory War UI Crash
Noticed an issue with the territory war reward screen causing crashes. Other screens besides the territory reward screen work properly. This particular screen is causing crashes when you tap back out of the rewards screen. Rewards remain the same as previous territory wars. Everyone should avoid this screen until we can deploy a hotfix later today.

Viewing the rewards screen shows a question mark reward but this is a UI bug. Also there are character shards that show up that should not be there. No plans to add new character shards to territory wars at this time.

We are planning to release a hotfix at approximately 4:15 to correct this issue.

Territory Battle Special Mission Requirements
There is an ongoing issue with Territory Battles Special Missions with the requirements for Special Missions not counting specific mandatory characters when trying to enter a battle. You can find more information about this issue here

Prestigious Quest Fulcrum Agent Tier 3 “Infiltrate”
We are aware of an issue with Prestigious Quest Fulcrum Agent Tier 3 “Infiltrate” not completing. We are working to resolve this quickly and should have it corrected by the next update.
Fixed in Update 04

This discussion has been closed.