How do I determine what is wrong with my Template submission

Ask for Help
1

Hi - my Template submission is rejected saying 'It appears something didn’t go as planned (etc)

I am a Free member therefore cannot use chat to ask how to diagnose the problem.

Any steps I can follow other than eliminating all the items in what a Template should not have?

image
image568×313 32.6 KB

3

Please review the Template Store Guidelines to see if you can determine what is causing this error to occur. If you continue to have issues, let us know and we can look into it further for you.

4

Hiya, I have looked through all the Guidelines and triple-checked (honestly) to the best of my knowledge.

I have shown this checklist. (Is the video actually mandatory maybe? I don’t have one yet)

Templates should:

  • Have privacy setting set as Users in the users table. Done
  • Have user profiles set up. Done
  • Be built in English. Done
  • Be visually appealing. Done
  • Be self-sufficient, stand-alone apps. Done
  • Be predominantly designed for internal business use. Done
  • Use neatly organized Glide Tables (i.e. clear formatting, functions/formulas computed in Glide’s Data Editor, grouped columns, etc.) Done
  • Avoid private or personally identifiable data and images (use fake names, stock photos, etc. to achieve this.) Done
  • Solve for a specific use case, and be really good at one thing (not mediocre at multiple things.) Done
  • Have a clear, complete description that includes the problem your template solves, its features, and its benefits to the end user. This will help more people discover your template via search engines. Done
  • Optional: Include a video that demonstrates the template’s features and explains its purpose. If you choose to do so, it must include a voiceover where someone explains the template—merely showing your template and moving your cursor over it is not enough.

Templates should not:

  • Contain private or personally identifiable information. For example, an Employee Directory template must not contain the real information of actual employees or people—it should contain fake or dummy data only. Checked not there
  • Contain offensive, profane, obscene, libelous, or otherwise illegal content. Checked not there
  • Contain any malicious or deceptive content. Checked not there
  • Contain visibility conditions: To make it easier for users to discover the features and components of your template, we suggest you avoid using conditional visibility, particularly on entire screens. Checked not there
  • Be a clone of an existing app or service. No clones of social networking or dating apps like Tinder, Facebook, or messaging apps. Checked not there
  • Be merely lists or indexes of content. For example, a template that consists of a list of jokes will not be approved. Checked not there
  • Rely on configuring third-party services or other additional functionality, whether free or paid, outside of Glide. In other words, your app should work immediately after someone copies it, with no additional setup required outside of Glide. Checked not there
  • Use HTML/CSS embedded within Rich Text components to inject styles or special functionality in the app that Glide doesn’t normally support. Checked not there
  • Contain advanced actions (multi-step actions) or integrations, which templates don’t support. Checked not there
  • Use the Experimental Code column. Checked not there