Please excuse me for asking a basic question.
I'm using auto translation to ask a question（from Japan）
The app that I had deployed to Heoku suddenly became unusable.
I haven't touched the app at all.
Please refer to the video from the start of the application until the error is displayed, as well as the terminal comments with 'heroku logs --tail' comand.
(the video is edited short. It actually takes about 50 seconds from the start of the application to the display of the error code)
enter link description here
Thank you,
Related
I've been moving step-by-step (as a webdev newbie) through the GatsbyJS installation via the Terminal. All looked great, except the Terminal appears "stuck" and I'm not sure how to resolve (i.e. whether to close Terminal app or let the process continue). It's been over an hour without any change in the Terminal prompt. Please see screenshot for detailed info. Any help would be much appreciated.
screenshot: Current state of Terminal app:
screenshot: Message when trying to close Terminal app:
Your terminal is not stuck. Everything works as it should.
It is listening to code changes which enables hot reloading. This way you can change code and you see the changes almost instantly in your browser. This makes for a pleasant developer experience and is industry standard.
Beware the old times when you had to manually restart your server everytime you made the tiniest code change.
Try opening a browser with url http://localhost:8000. Change some text inside your index.js. You should see it reload in the browser.
I've been trying to use batch testing to test my luis app and have been experiencing an annoying bug. Basically the LUIS app page will become unresponsive while the batch testing window is open.
The most similar issue I've seen can be found here: LUIS web interface crashed after import JSON file for Batch Testing or Import App, with no answer yet.
My problem is also slightly different by the looks of it.
Experimenting has yielded the following results:
I can upload, test and view the results of 1 batch successfully sometimes. Sometimes the page will become unresponsive while I am looking at the results.
If I have successfully viewed the batch, but then close the batch testing window without deleting the batch, the next time I open the window the whole site will become unresponsive.
Recently opening the "Inspect" tab on the single utterance testing window has also begun making the page unresponsive.
I can submit images if needed, but the pages seem more or less the same after the bug has occurred, they simply stop working. Pressing buttons does nothing and I need to refresh the page if I want to get back to the bot's Dashboard/Build/Publish/Settings page.
The app has 18 intents, 12 entities, and a couple hundred utterances. I have tested it on a collaborator account and the bugs seems to occur there too. Not sure what other info might be relevant.
If anyone has experienced similar issues and can help I'd appreciate it. Being able to use the built in Batch Testing feature would be very useful.
When starting the Xamarin profiler it successfully starts the application on my iPhone device.
However before the profiling begins I get an error at the bottom of the window that states:
Afterwards it states
Sorry something went wrong. An error occurred on client profile while executing a post topic
Any idea how to fix this?
Well something is wrong with the Provision Profile you are creating Either Create it again or Upload a little bit more than this so we can understand what the actual problem is.
I can't find much documentation around this issue. All other running apps on my pebble have a connection to my phone, and work as expected. However, a Pebble.js application I'm currently working on simply displays Disconnected - run the pebble phone app.
I have noticed that in my Developer Settings that the Connection Manager is listed as Disconnected. Is this part of the problem? I see nothing in the logs.
For reference, the application is doing a simple ajax request and displaying the result.
This message is often caused by the JavaScript crashing on the phone (undefined reference, unknown function, etc) and so the watch thinks it is not running.
Some ideas to debug this:
Replace your code with one very simple console.log("hello world") statement and see if this works.
Look at the Logs (View Logs button in CloudPebble or pebble logs on the command line).
Very rarely, on Android, I have seen situation where the Pebble app is in a bad state where it cannot execute the JS for only one app. When this happens, you need to force-kill the Pebble app and relaunch it.
I have had the same experience.
I usually kill and restart the pebble app on my phone and then I also do refresh the browser. Sometimes you have to log out of and then log back into Cloudpebble.
I have made a Windows Phone app (for WP7.1) that uses BackgroundAudio for streaming, nothing too complicated. It was approved and made available for download in the store. However it no longer works, i.e. the app worked in debug+release when run from VS2012, and I assume the .xap I uploaded worked since microsoft approved it (they rejected it once and I was able to reproduce and fix the bugs they reported).
When downloaded the app simply bails on load on WP8 (lumia 820) i.e. flips back to the tiles immediately.
On WP7 (lumia 800) but the playbutton ignores input, however it downloads and displays the playlist, so some kind of functionality+network connection works.
I have tried the basics: installing using the application-deployment tool (app working), running the "Store Test Kit" which reports some slowdowns in the UI animations, but nothing serious (I hope).
Any ideas how to reproduce ".xap approved and downloaded from store but not working" or getting debug info from the phone without VS? Or any other things i can try out?
Every time your app crashes it will be logged and reported on your Windows Phone Dev Center Account. Just go in there and export the details to excel. Get the stack trace and put it in here. Maybe we can help.
The very first thing i can tell you is the opening page has some exceptions and that too it doesn't go well with some phones. Seriously there are concerns when a wp7 app is ported on wp8 device and vice-verse. To the extent of my knowledge there might be some binding issues. make sure you got the binding class to be public. And just as #AMR mentioned go the dev center and export the stacktrace. Try resolving them. Moreover if an app get certifies, it doesn't mean it is completely error free. The tests are limited to very coomon errors only.