WardrobeGo

A LITTLE HELP GOES A LONG WAY

Let’s keep
things simple.

Answers for your wardrobe, your photos, and the homes you share.

Need a hand?

Tell us what you were trying to do and what happened. Please keep private wardrobe details out of your message.

[email protected]

THE EVERYDAY QUESTIONS

A few helpful answers.

Can I use WardrobeGo without iCloud?

Yes. WardrobeGo starts locally on your iPhone, with iCloud off. You can add, edit, browse, and delete clothing without a separate app account. Enable iCloud in “Wardrobe options → iCloud & sharing” only if you want to sync.

What happens if I turn iCloud off?

Sync pauses; it does not delete your saved clothing, photos, or existing iCloud data. Private clothing remains editable on your device. Downloaded shared homes become browse-only until you enable iCloud again.

How do I organize clothes across homes?

Add a home, give each clothing item a name, type and owner, then choose where it belongs. Rooms are optional. Use the wardrobe filters to browse a home or person. Changing an item’s home clears its old room selection.

Can I use an illustration instead of a photo?

Yes. Choose a garment illustration and color in the clothing editor, then tap Done to apply it. Photos and rooms are optional. Changing the picture does not change the item’s clothing type.

Why doesn’t a photo cutout look right?

Photograph one garment on its own with a clear background. The on-device tool detects foreground subjects, not clothing specifically. Choose the correct subject, adjust the crop, or keep the original photo if the result isn’t useful.

Does joining a home share my own private wardrobe?

No. Invitations give access to the selected home only. Your private homes stay separate. Shared members can view and edit the invited home, so share only with people you trust.

“Invite Family” says sharing needs attention. What should I do?

Keep your wardrobe as it is. Confirm iCloud is enabled in WardrobeGo, your iPhone is signed into iCloud, and you have an internet connection. In the sharing screen, use the details option to copy the app version, failed step and Apple error codes.

If private sync works but invitations fail, the app’s Apple sharing setup may still need attention. That is not fixed by a permission prompt. Do not delete homes, reinstall the app, reset databases, or remove saved clothing to try to repair sharing.

For the app owner: check the sharing schema
How do I stop sharing or leave a home?

The home owner can use “Manage invitations & access” to remove participants or stop sharing. Invited members can choose to leave the shared home. These actions require iCloud and an internet connection. Other people may still have copies of information they previously saw.

FOR THE APP OWNER

When Apple’s sharing type is missing.

Apple uses a system record type called cloudkit.share for invitations. Private wardrobe sync can work even if this type is not yet deployed. TestFlight and App Store builds use the Production environment.

  1. On your Mac, run the separate WardrobeGo Sharing Setup app from Xcode on your test iPhone, using Debug and Development signing. It has a different app identity and no wardrobe storage. Do not replace your existing WardrobeGo installation or reset the container.
  2. Sign the test iPhone into iCloud in Settings, then choose “Create test share” in the setup app and confirm. It saves a private share for a dedicated empty test zone and checks it on Apple’s server. It does not send invitations or access your wardrobe. Apple creates the system sharing type through this save; do not manually create a normal record type with that name.
  3. In CloudKit Console, confirm cloudkit.share appears under Development → Record Types. Select “Deploy Schema Changes” and review the additive changes before deploying to Production.
  4. Confirm the sharing type is present in Production, then verify inviting, accepting and editing with the new TestFlight build on two real iPhones.

If deployment does not show the new type, stop and contact Apple Developer Support with the container ID and schema evidence. Do not use “Reset Environments” on this project to troubleshoot.

Read Apple’s explanation