# Duplicate App Not using copy of spreadsheet

**URL:** <https://community.glideapps.com/t/duplicate-app-not-using-copy-of-spreadsheet/3390>\
**Category:** Report a Bug\
**Created:** [January 7, 2020, 2:40am UTC](https://community.glideapps.com/t/duplicate-app-not-using-copy-of-spreadsheet/3390 "2020-01-07T02:40:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Valleygirl](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/valleygirl/32/2514_2.png) [@Valleygirl](https://community.glideapps.com/u/Valleygirl)\
**Post date:** [January 7, 2020, 2:40am UTC](https://community.glideapps.com/t/duplicate-app-not-using-copy-of-spreadsheet/3390/1 "2020-01-07T02:40:03Z")

</div>

When I duplicate an app (one created about 2 months ago), it does not use the created spreadsheet duplicate.

Steps:  
Duplicate App, select “Copy the sheet”  
Note that there is a new spreadsheet "Sheets for Copy of "  
Edit the duplicate app, and select “Edit Sheet” note that it shows the original sheet, not the copy  
Make changes to “Sheets of Copy of \<App.”, they are not committed to the app

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 7, 2020, 2:57am UTC](https://community.glideapps.com/t/duplicate-app-not-using-copy-of-spreadsheet/3390/2 "2020-01-07T02:57:02Z")

</div>

I can confirm this. Selected Duplicate App, Selected Copy the Sheet and then Duplicate App. Like @Valleygirl says, it creates a copy of the sheet, but still syncs to the original sheet.

---

<div class="post-metadata">

**Author:** ![Mark](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark/32/125_2.png) [@Mark](https://community.glideapps.com/u/Mark)\
**Post date:** [January 7, 2020, 5:00am UTC](https://community.glideapps.com/t/duplicate-app-not-using-copy-of-spreadsheet/3390/3 "2020-01-07T05:00:25Z")

</div>

This should be fixed now. Apologies for the trouble, and thank you for reporting!