# 5.7.0 - Could not overwrite project properties file

**URL:** <https://forums.unrealengine.com/t/5-7-0-could-not-overwrite-project-properties-file/2675683>\
**Category:** Mobile\
**Tags:** ARCore, unreal-engine, Android, Augmented-Reality\
**Created:** [November 16, 2025, 9:57pm UTC](https://forums.unrealengine.com/t/5-7-0-could-not-overwrite-project-properties-file/2675683 "2025-11-16T21:57:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![FrankiePibbs](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/frankiepibbs/32/918637_2.png) [@FrankiePibbs](https://forums.unrealengine.com/u/FrankiePibbs)\
**Post date:** [November 16, 2025, 9:57pm UTC](https://forums.unrealengine.com/t/5-7-0-could-not-overwrite-project-properties-file/2675683/1 "2025-11-16T21:57:42Z")

</div>

Cannot compile in Android (AR Template), nor configuring it on the project Settings / Platforms.

Runningt AR Template on 5.7.0

Any ideas?

---

<div class="post-metadata">

**Author:** ![ShadowBr0kerz](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/shadowbr0kerz/32/1201558_2.png) [@ShadowBr0kerz](https://forums.unrealengine.com/u/ShadowBr0kerz)\
**Post date:** [September 12, 2026, 10:59am UTC](https://forums.unrealengine.com/t/5-7-0-could-not-overwrite-project-properties-file/2675683/2 "2026-09-12T10:59:57Z")

</div>

“could not overwrite project properties file” is not an engine problem — windows is locking or read-only-flagging a file under intermediate/android. it shows up on the ar template first because that is the first time android tooling runs gradle. fixes in order:

1. close the editor (and rider/visual studio), then delete intermediate/android entirely. it regenerates on the next build; a stale locked copy is the most common cause.
2. 
  1. check the folder is not marked read-only. projects copied from a zip/backup, or living inside onedrive/google drive sync, come in read-only or get files locked mid-build. clear the read-only attribute recursively, or move the project out of the synced folder and pause sync while building.

3. 
  1. kill lingering gradle daemons: gradlew --stop (or end java.exe processes in task manager). a daemon holding old file handles produces exactly this error on the next package.

4. 
  1. if the project was moved between drives, also delete intermediate/projectfiles, regenerate project files, and re-check the SDK/NDK/JDK paths in project settings → platforms → android still resolve.  
after wiping intermediate/android the first package takes longer — that is normal, it is regenerating the whole gradle stage.
