Unfortunately plugin developers don’t get to see crash reports unless you send them directly to us by hand. I know that’s a bit of pain, but I have no control over that I’m afraid.
If you’d like one-on-one help, I really recommend visiting my Slack channel I post about it continually here on the forum – and I know you’ve been a regular here for years, so please excuse the reptitive linking:
If you send me a project that’s having problems like this, along with your RW evenironment, I can see what you’re seeing and we can work on the problem together.
Instead of sending those off to a support request, you can drop them directly on a private slack chat and then I can run your project in a debug environment and see what you’re seeing.
I just wanted to mention, over on the slack channel (i post the links to the slack channel enough that the forum bot yells at me if i try now – LOL) I posted a beta version of Stacks that did manage to clear up the crasher that @TemplateRepo mentioned a few pages back in this thread, and it also corrects a bug that prevented drag and drop from one project to another that i think may have also come from this thread (although I couldn’t find the exact one).
So, I just want to say, hey… see? the system kind of works sometimes: @TemplateRepo was nice enough to meet me in slack, dragged his test file and rw-environment over into our chat and 10 min later i was able to duplicate his issue with ease.
And… well… it was actually a really hard bug to fix. It took about 4 days, but the fix did happen. and boom. Problem solved. Beta tested. Fix confirmed.
So, if you have a problem – especially if it’s a crash, I’d love to hear from you. Please jump over to the slack channel, and we can give it a whirl.
@johntalbot - the latest beta specifically fixes a crash related to copy/paste. i’d be very curious to know if it corrects the crashes that you’ve been seeing. and if not, i’d really appreciate a crash report and/or any of your projects/rw-environment files if you have time.
unfortunately without direct input from users it’s very difficult for a plugin developer to fix a crash that occurs for some users but not others. the automatic “Send to Developer” crash reports that pop up after a crash go to Apple or Realmac – but never to me.
however if you copy and paste that info into a file, and send it my way – even better with a file/rw-environment – then i can usually fix them. crash reports (mostly) contain very specific information about what went wrong. sometimes it’s so specific that i can fix a bug in ten minutes. other times it takes a weeks – but that’s just how development goes.
@isaiah The reports went to Apple. I will check out your Slack channel. At the moment my project is behaving, so nothing to fix now. Thanks for your reply.
Just need to wrap up details and I’ll send out Stacks v4.2.1. So look for it in a few hours. Worst case, tomorrow.
I mostly wanted to say thanks to everyone who helped out with the bug hunting, beta testing, and crash-report sending. Especially folks who stopped by the slack channel.
Thank you so much.
just to wrap this one up: not a plugin issue – so i’ll try to be brief since it’s a bit off topic for this thead. @bruce sent (via Slack – thanks @bruce!) a spin-dump file from the hang when RW beachballed.
the report shows that RW seems to be waiting for authentication to something. maybe a resource? maybe an account? but this is occuring before any plugins load. my guess the resources think they’re on another drive somewhere and RW’s waiting for that to be mounted or the time out. that would jibe with the the obvious missing data from the file too. i talked to @bruce a lot more about the details – but it seems working for now (¯\_(ツ)_/¯ – mysterious self-fixing things scare me – but better than broken i, right?)
if anyone else has similar issues, i’d recommend zipping the file up and sharing it with me and probably @tpbradley – i’m happy to help users work the problem, but the internals of why this might be happening are probably more in @tpbradley’s domain.
onward…
a little future thinking here: if anyone finds any issues in the new v4.2.1 release, send them my way. visiting the slack with your crash reports and rw-environments is always extra appreciated. thanks!
@Pyrobrit: i chickened out.
or rather, the filter for “autofocus” – the thing that’s stealing the insertion point while editing text and tabbing between controls was a bit more delicate than i had originally thought.
so one last quick beta is being pushed out now. it’ll go up on the auto-update servers as v4.2.1 beta 3 just as soon as it finishes running automated tests and Apple notarizes the build.
if you’d like to test it, jump over to the slack channel (links above) and grab it – don’t forget to let me know how it goes.
and with that – after a very long day of code – i think it’s time for a nap. good night.
Did the upgrade to 4.2.1 and one of my site builds crashes on rw load. Others using the same framework were okay, so maybe it’s a stacks conflict. Downgrade stacks and all is well again. How do I send a report?
"If you’d like one-on-one help, I really recommend visiting my Slack channel I post about it continually here on the forum – and I know you’ve been a regular here for years, so please excuse the reptitive linking:
If you send me a project that’s having problems like this, along with your RW evenironment, I can see what you’re seeing and we can work on the problem together.
Instead of sending those off to a support request, you can drop them directly on a private slack chat and then I can run your project in a debug environment and see what you’re seeing."
i’d really appreciate looking at that project file. i know the problem is solved for you by moving back a version, but it would be great if we could solve this for everyone. And I probably will never find out about this crash unless some kind person shares the details with me.
In specific, a crash report, project file, and rw-envioronment would really help.
Sorry for the late reply. Out of town and catching up. File is now opening with latest Stacks update 4.2.2, although it seems changes in that version may not have made the difference. It could very well have been something in the file as we are making many changes and tests on the home page only. It’s a large site over 100 pages. I sure would love to have responded when the issue appeared, but time was short.
i’ve had a similar bug reported 3 times. each time the when i followed up the result is the same: it didn’t work, but now it does.
i’m glad the problem is not hindering you anymore. but if you bumped into it once, there’s a chance you’ll bump into it again. if so, make sure to save a copy of the file so you can share with me.
for anyone else posting to this thread: please save as much data as you can about the problem.
the more data i have about a problem, the more i can help.
@artista: This is entirely off topic. And totally unsolicited advice, so I think if you have any reply – we should move it to another thread…
but with that stipulation, here goes:
Often when I see projects of this size it indicates a problematic use-case.
In these cases the projects contain a few unique pages but the vast majority of pages are nearly identical. An example is an online store site with 85 product pages and 15 other pages about the company.
Creating 85 similar product pages is possible in Stacks. Using Partials to manage the duplicate content makes maintaining them pretty easy – but there’s still a MUCH simpler way to do it: A CMS.
A Content Management System lets you create one product template page and then *merge it with a *database of 85 products – your visitors see 85 product pages as if you’ve created each one by hand.
Adding/removing/changing products is as simple as editing the data – the site then automatically updates itself.
I’d strongly recommend asking yourself if your use-case falls into this category.
If so, today is the best day to stop building more similar pages in RW and spend a few hours looking into a CMS. Don’t fall victim to the “sunk cost fallacy” – the time spent moving to a CMS will be recouped almost immediately.
There are many great CMS’s that work with Stacks. If you search this forum you’ll get a lot of info about them. If you’re unsure your use case is appropriate, asking on the forum is always a good way to begin.
* i’m using “merge” and “database” here in the most general sense. Not all CMS systems use a database or merge per se. Some use JSON files, text, etc. How a CMS does it’s work is not super important to the discussion here. What is important is using a CMS instead of doing repetitive work.
I couldn’t agree more.
There are tools who offer different solutions for different use cases.
It’s always interesting to see how Rapid Weavers is used, but that reminds me the days where ppl used power point for graphic design work and still use Excel as a database tool. It works, some how, but the time spent to “bent” your problem into a solution that fits could be better invested in getting the right tool for the job.
And to be fair, we have similar paths seen with Wordpress, which is by heart and it’s architecture still a blog and now used as a content management system for everything between a single pager up to large news sites or ecommerce solutions (using woocommerce and the like) - it works somehow, but not really on a professional level - that’s me saying, having written tons of plugins for wordpress / woocommerce.
I have been having the same problems. I get the quit unexpectedly report and have reported a few times. I just downloaded the stacks beta and am trying to see if it is more stable
currently there is no difference between the beta version and the release version other than the version number.
and have reported a few times
unfortunately “reporting” only reports things to Apple and to the app developer – which means that I don’t see a copy of that report.
i only see crash reports when folks like you send them to me or post them to a forum like this. it’s not always required, but the most helpful would be to post:
a crash report
a brief description of what was happening right before the crash happened. it’s usually helpful if you can tell me the exact button you clicked or exact thing you typed immediately before the crash.
p.s. i have mentioned all of this info at least once or twice in this thread – the forum actually gets upset with me for posting this links over and over LOL .
it’s a mega huge thread, i wouldn’t expect you to have seen this info, but i just thought i’d mention that if you feel stuck by this situation there is lots more good stuff in this thread about things to try, how to get crash reports, how to contact support for Stacks, etc. so if you feel a bit at a standstill have a read through.
the more info i can get about a crash the more easily i can fix it. i believe the two crashes that were reported earlier in this thread have both been addressed. although all crashes seem very similar, often they have very different root causes, so never assume that i have heard about your particular crash.
i’m currently researching two other crashes that were sent in one yesterday and one a few days ago. it will be interesting to see if your crash is the same as one of those are another third unique crash.
's – so it’s past time get this out to everyone asap. 
