Just had this where a child object with a kinematic trigger collider and rigidbody (not moved, except by collider and rigidbody on parent) wasn't updating the physics transform.

Using "transform.localPosition = transform.localPosition;" in the update fixed it for me.

I have updated Unity to 2018.2.5f1 and still have the issue. I'm animating my game object which has mesh and collider by scaling it down. Collider updates when I reenable Box Collider itself or reenable it's IsTrigger property. I noticed that collider updates correctly when I put my game object into another empty game object and when I animate this empty game object's scale instead of my game object's scale.

After some testing I've discovered that 2018.2.4f1 doesn't seem to sync transforms automatically in editor anymore if transforms are moved without a rigidbody.
Despite Physics2D.autosyncTransforms being enabled, if I move a transform with a collider2D in update without a rigidbody, unity editor doesn't sync the transforms on move. (Which may end up being a good thing performancewise).

But if I manually call Physics2D.SyncTransforms after every move, the unity editor properly updates the collider with the movement. This may be an intended change since transforms with rigidbodies don't actually 'move' anyway until the physics step, but in my case I need immediate transform movement.

I'm having this issue after updating from 2017.x to 2018.2.4f1. It only happens for my objects interpolating with this method: http://www.kinematicsoup.com/news/2016/8/9/rrypp5tkubynjwxhxjzd42s3o034o8

I've been doing it this way since ~5.6 and have never had issues before. It only happens in editor playmode where collider isn't matching the transform movement immediately. If I move the transform, then refresh the editor in some other way (like clicking on inspector or clicking a tool in editor), the collider will then update to the new position. But it's not automatically updating anymore.

I too had this bug fixed by updating to the latest Unity version

Can also confirm it is fixed in 2018.2.3f1, just confirmed it in my repro project: https://unity3d.com/unity/whatsnew/unity-2018.2.3

"Physics - Fixed an issue where a Collider's underlying PhysX Transfrom did not update correctly when reparenting."

it's fixed on the 2018.2.3f1 !
thanks

Also, I have got this issue on the Unity 2018.2.2f1. I updated from 2018.1.0f2 to 2018.2.2f1 and after running my project, game objects which ware Instantiated from prefab, them colliders didn't work correctly. Game Objects with the Rigidbody component could go right through these.
Rigidbody:
IsKinematic = false
Colliders:
IsTrigger = false

But if I use this code in Game Objects which were ware Instantiating from prefab, Colliders were working.

private void Start()
{
Collider mCollider = GetComponent<Collider>();
mCollider.enabled = false;
mCollider.enabled = true;
}

When I changed Unity version on 2018.1.0f2 from 2018.2.2f1, everything started working correctly as it worked before the update.

on version 2018.2.2f1