Partition projection misbehaving on inserts in Athena engine version 3

I'm testing our application's compatibility with Athena engine version 3 and am finding that queries that insert into a table with partition projectioning enabled, which worked fine in Athena engine version 2, do not work in version 3. A very stripped-down version of what we normally do - with complete success in engine version 2 - is:

CREATE EXTERNAL TABLE test3 ( field1 STRING ) PARTITIONED BY ( field2 STRING ) STORED AS PARQUET LOCATION 's3://bucket/data/' TBLPROPERTIES ( "parquet.compression" = "SNAPPY", "projection.enabled" = "true", "projection.field2.type" = "injected", "storage.location.template" = "s3://bucket/data/field2=${field2}" )

INSERT INTO test3 SELECT '2022-11-11' AS field1 , 'dev' AS field2

In engine version 3 that throws a NOT_FOUND: Partition 'test3' not found. error message, even though the resulting S3 data file is created.

Is anyone else doing any ETL-like SQL insert statements in Athena, with partition projectioning, and having any success in engine version 3?