Tim H

Have you tried updating the save file on the console where it works? Place a couple of blocks, walk around. Then save & exit and try other console. This worked for me. 

I just checked and sync between Xbox One and Xbox One S worked for me. I updated the game, turned on the save file to update it, then synced it on the other Xbox. I appeared on the same spot with the same block I placed in front. I still have not checked if there are any chunk errors like those that happened to me before but I can confirm that the sync, in general, works. Thanks, Mojang!

I have an Xbox One and Xbox One S and can confirm that the sync of worlds does not work. 

Hello,

I am having the same problem with my saves. I have an Xbox One and Xbox One S at home and alternate between them when I play. My minecraft save transferred once but with a ton of bugs. The entire first floor of my house went missing as well as anything on the same level including close by structures. The ocean monument near me which I raided got restored and the zombie villagers I cured disappeared. It was as if the newest save was merged with an older one. After that I fixed the damage although some chunk glitches appeared (Large square holes leading down to the void.)

Recently it synced once and was without errors. However today I tried to sync again but after a long syncing process, a message popped up saying that the save file is damaged or improperly synced and that I should try playing it where it is ok and try to think again. I did that. It didn't help. I even deleted all saves from the console and manually transferred the save data from the external hard drive of the other Xbox. Still the same message shows up.

Not sure why the issue is marked as "Resolved." A fix to the problem would be appreciated.

Thanks

@Pokechu22 It's funny how you always state "The behavior wont be removed" as a fact and say "This still is considered not a bug" even though Grum, AFTER marking this at "intended", clearly said, i quote:

"I share the opinion that this 'non-direct-connectivity-still-powers-a-piston' is a bug. It's confusing for everyone but a small niche of experienced redstoners. ... So in order to possibly get this non-direct-connected-powering removed, I think we need to solve all the problems above, which in theory shouldn't be too hard if we work together."

So please stop lying to people to portray your personal standpoint as irreversible fact.

Fact is, though, that this IS a bug (clearly and undeniably so) that negativly affects the gameplay experience of countless players (pretty much everyone who ever used or ever will try to use pistons). Calling it a "feature" won't make it go away because it won't stop to negativly affect the experience of players. And that's why complains will never stop until the regular crafting recipe will create pistons that are bugfree and work just as one would expect. Pistons are supposed to have only one behavior, to be extended when powered in an obvious way and retracted when not. Nothing else. Nothing intermediate.
The bugged pistons could remain on the current IDs, though, to maintain backwards-compatibility and to allow to spawn them in creative mode after the crafting recipe has been moved to the fixed pistons, so i don't know why you are still vehemently fighting a fix.

I don't think it's necessary to have a recipe for the BUD pistons at all. Usual survival players don't know of the BUD behaviour and expect a bugless piston. Bugless survival mode should be the goal to strive for after all. Those who use BUDs rather use it for mapmaking or experimental builds and would use the creative menu or the /give command to get the pistons anyway.

Yes, bugs can lead to good things, that is, if they don't negatively affect the experience of players. This bug, however, HAS a negative effect that leads to illogic behaviour (pistons getting stuck in states they shouldn't be in, etc.) and prevents people from building machinery that SHOULD work by all logic means. I can't believe keeping a bug like this in game is even open for discussion, let alone accepting it as "intended". If a bug is needed to provide functionality that the main game doesn't provide, then something is fundamentally wrong. If the functionality is necessary, provide an item or method that provides it WITHOUT negatively affecting the experience of legit players. That the bug has always been in the game is not a valid argument for it's existence. Also, a fix breaking existing machinery is not an argument either, because everyone who (ab)used it could clearly see that the illogic behaviour could have never been intended and thus might get fixed in the future.

However, all idealism aside, keeping the current Block IDs as pistons with the bug for the sake of backwards-compatibility and having new fixed piston blocks for crafting and the creative menu would be a compromise that should acceptable for everyone, because all would get what they want and noone would get harmed in the process. Legit players would have a bugless experience, existing contraptions would not break and mapmakers who like to use the bug can just spawn in the old pistons via /give command.

@William Pearson: Keeping a bug in the game that destroys legit and logical mechanisms in order to allow other illogic mechanisms that exploit bugs and were never meant to be in the game in the first place, where's the logic in that? If certain things like some piston doors or 1x1 displays can only be achieved by exploiting bugs then it has to mean one of those two things:
1) They aren't meant to be possible in the game and shouldn't exist.
or 2) They should be possible in the game and thus shall be made possible by either adding new redstone devices or by changing current redstone devices to provide this functionality in a LOGIC and intuitive way.
The current behavior, however, is just plain BROKEN.

Thanks to this bug pistons are severely messed up and building any larger piston mechanism becomes a guess-game and timing hell. I can't believe this bug still isn't fixed or at least scheduled for fixing.
It's also very odd that some people suggest to keep this bug in the game... it's a BUG that breaks countless legit builds. To keep it in just because exploiting it's side effects can be (ab)used sounds insane to me. If the unintentional functionality provided by the bug is so useful then it should be provided as a seperate item/feature!

Hoppers should only fill the input slot and pull out of the output slot of a furnace, IMO. It would resolve this bug and would make the hopper/furnace combination actually useful.