Once this update has ironed out the bug and live, I am assuming it would solve this problem? Just double checking