Firstly sorry if this place does not deal with questions like this, I have tried the tutorials online for App Inventor and I cannot seem to find anything relevant.
Basically I am downloading App Inventor 2 which has given me no issues, however when I try and connect to the emulator it fails. It states that 'Your companion is out of date', the tutorials online told me for this I would have to download the latest software (which I already had but I uninstalled and tried again). After getting the same response a few times I managed to get through to another screen that stated 'Unable to send update through to device/emulator' and on the actual emulator it just states 'Parse error - There is a problem parsing the package'
Does anyone know what is happening here?
Related
I'm using several Google API for a professional project for 6 years now (Maps, Places, Firebase, etc).
All of a sudden, the project stopped working yesterday evening. When I tried to figure it out on the Google Developers Console, the project is gone, pure and simple.
There is no trace whatsoever on the dashboard and all my credentials are missing!
I never got any prior notice from Google, and since you need a valid project to contact support, I'm 100% stuck...
Does this already happen to someone here?
One of my Flutter app on store an that app is integrated with Sentry client for crash reporting.
I got a few crashes and I have fixed most of them based on logs it provides and all I can say Sentry is one of the good solutions for the crash reporting in Flutter.
Unfortunately, I have one crash(Many users are facing it currently) there but I can't able to figure out what it is all about and what should I do to close that issue.
Here is just an overview of an issue and same in the details nothing much on EXCEPTION like stack-trace or so.
Here is the public share-able link for the same.
Anyone has faced similar kind of issue or any clues which can help me to get direction here?
Doing some searching for this, I have found that this is caused by CachedNetworkImageProvider.
In my case, the issue seems to be related to flutter_map and it is raised here: https://github.com/johnpryan/flutter_map/issues/245 - there is also a video link on how to fix this apparently (not sure).
I've also seen this raised in production a few times with very little other information. (The incorrect spelling of retrieve, means it's a bit easier to search for where this issue happens).
For some reason, I can't publish articles using custom CMS solution we have made in Laravel. The developer which made this does not work with us anymore, and client requested to change the facebook page. He used this SDK: https://github.com/facebook/facebook-instant-articles-sdk-php
New Facebook page needs to go through verification for instant article.
So, when I set development_mode=false, I get the error "This page has not been accepted in the review process for publishing Instant Articles yet", which is fine, that error is expected.
But, when I change to development_mode=true, nothing happens, no errors. The request went without errors, but article was not published in the Development Articles.
Any idea what might be the problem here?
Although I don't appreciate negative down-votes, since this was not the problem with the code, the solution for this problem was manually posting first 10 articles. No matter what, SDK could not publish anything, nor in development nor in production mode, until I published 10 articles manually.
I'm trying to create a blank Xamarin project in VS 2015 Community. It always fails with the error: the targetPlatformVersion cannot be null.
I've uninstalled 2015, repaired 2015, installed the Tools 1.4.1 SDK over and over again with varying results. The 'varying results' is strange to me. Sometimes it takes over 10 hours for the repair/reinstall to complete.
I really want to learn about this tech, so I reached out to the Xamarin team and this was their response:
"Hi Stephen,
We do not do code reviews. I would suggest contacting UWP support to get more insight on the problem.
Below is more information on how you can acquire support for this. You can also post your query on Stack overflow or MSDN forums.
https://developer.microsoft.com/en-us/windows/support
Warm Regards,
....."
I stated:
"Sorry to be an idiot about this but what does ‘we do not code reviews’ mean?"
Their response:
"Basically we do not look at the code that is generated by customers. That was just a side note.
This seems to be like an issue with UWP. You can email UWP support to get to know the reason for this error. If they direct you to contact us, we can probe further."
I've tried to post my configuration, but stackoverflow doesn't like the format of my posted config info...apparently it needs to have four spaces and my didn't.
I can hopefully post that info upon request.
I am using Microsoft's AdControl in my app that I am developing. I have registered at pubcentral and using the correct ApplicationID and AppUnitID. Also, setting the AdControl.TestMode = false. The ads were getting displayed correctly yesterday but today, I get this error - An unexpected error occurred during response processing (Name: ECN).
Has anyone else noticed this issue?
I am using January 2011 tools for WP7. Not sure if this is an issue with the Emulator.
Edit: Just a quick update. My app with ads that weren't working during development got published this morning and all of the ads are working when I downloaded it straight from the marketplace. Still not completely sure of the reason but I thought that information may be useful.
Ok - I've spent far too much time researching this. Apparently there are a lot of people having this error. I think it may have something to do with the impending update of the WP7 because it's relatively recent. If you check out the official forums (http://community.microsoftadvertising.com/forums/32.aspx) there are tons of posts describing the same issue.
For some reason I am still getting impressions with my AdControl despite the lack of visual advertisement. My suggestion is to leave the code in your app and try and publish it (this is the route I'm going to take at least) and hopefully they will start serving ads again soon.