Linking inconsistency between closed app and open app deep link

When I do the following deeplink myApp://detail/123 (123 being an ID) with the app being closed and the following config

screens: {
  detail: {
    path: 'detail/:id',
  },
},

I'll get the correct state

{"key": "detail-SbcExuYkpp6-Y4u9rYWjO", "name": "detail", "params": {"id": "123"}}

but if the app is already open (foreground or background), and I send another deeplink, then this is the state I get

{"key": "detail-vqAsOQ3ZBfydQjUCcpX9e", "name": "detail", "params": {"initial": false, "params": {"id": "123"}, "screen": "detail", "state": undefined}}

So for some reason, you get a nested params

Start by reproducing the myApp://detail/123 deeplink with the app closed and then foregrounded or backgrounded, using the shown detail/:id configuration. Compare the resulting navigation states and identify why the open-app case nests params; done means both launch states produce the same parameter structure.