[FIXED] Unable to finish quick "Build an app in 5 steps"

What I’m trying to do:

Go through the quick interactive utorial that you get when you first sign up and log in.

What I’ve tried and what’s not working:

When getting to the part that says “Double click the button” (step 4 of 5), the dialog never updates, and the prompt never goes further, even though I’m already at the code box to enter stuff. This means I can’t finish the tutorial.

The error in the console log is:

app.js:11 Assertion failed: TypeError: Cannot read property ‘newIDE’ of null
at y (PropertyTable.js:65)
at PropertyTable.js:141
at f (rsvp.es.js:320)
at A (rsvp.es.js:492)
at C (rsvp.es.js:478)
at MutationObserver.ue (rsvp.es.js:2432)
(anonymous) @ app.js:11
trigger @ rsvp.es.js:180
(anonymous) @ rsvp.es.js:1020
setTimeout (async)
he.after @ rsvp.es.js:2471
e._onError @ rsvp.es.js:1018
b @ rsvp.es.js:410
ue @ rsvp.es.js:2432
characterData (async)
(anonymous) @ rsvp.es.js:2409
se @ rsvp.es.js:2366
w @ rsvp.es.js:429
g @ rsvp.es.js:394
y @ rsvp.es.js:402
(anonymous) @ rsvp.es.js:522
u @ DesignerIframe.js:84
dispatch @ jquery.min.js?sha=87083882cc6015984eb0411a99d3981817f5dc5c90ba24f0940420c5548d82de:3
q.handle @ jquery.min.js?sha=87083882cc6015984eb0411a99d3981817f5dc5c90ba24f0940420c5548d82de:3
Walkthrough.js:78 Uncaught TypeError: e.parse is not a function
at Walkthrough.js:78

This happens every time you double click a button in Walkthrough mode.

Obviously I can proceed anyway, just figured I’d give a heads up of what’s happening :slight_smile:

What I’m trying to do:
Finish the tutorial
And
Deleting the test app my test app “tut1”

What I’ve tried and what’s not working:
Advancing from step 4 did not work in two browsers

And

Deleting my “tut1” app is not working

thanks for reporting - we’ll get that fixed

OK, thanks. Deleting the test app worked. It had a visual issue where it would show a scrollable area and I had to scroll down to see the Delete This App link. Not the most noob friendly way to do things :stuck_out_tongue:

Thanks for reporting the issue! This has now been fixed.