I've just submitted my first app to the App Store and I have problem with description field in iTunes Connect - it does not allow me to enter multiline value.
I've tried everything - copying-pasting from different editors, entering manually, etc.
If there is one line, like "Hello world" - it saves successfully.
When I've got at least 2 lines of text, lke
"Hello
World"
it just shows me the following error message and does not save:
Description cannot contain control characters (for example, null, new lines, carriage returns, escape, and other invisible characters).
Unbelievably this bug is back!
You can use Google Chrome, it's just broken in Safari.
Don't worry, this just started this morning, and is a bug that Apple has acknowledged. Hopefully this will be fixed soon. There are a lot of very unhappy people, me included, who can't get out important updates.
Posting this as an answer since I can't yet comment.
Not being able to enter multiline descriptions is an existing bug that only seems to occur sporadically. It is currently broken as of 8 hours ago on Chrome 51.0.2704.103 and Safari 9.1.1.
You can work around it by removing newlines, or waiting until Apple fixes the issue.
I'll report back when I see it fixed (I'm expecting the fix to take a day or two).
Edit: As of this morning, submitting to the App Store on Chrome with multiline descriptions is working!
Related
I just bought a barcode reader from China model Honeywell HH400. It works perfectly when I use it other device. But now I use it in my web application and I am getting a problem. It always toggle Chrome developer console. I also tried scanning barcode into URL bar, and it does the same. Does it have an event to trigger F12 what? Or misconfiguration with the scanner that I don't know?
I am sure that you might have already received a solution.
But for others who might come across this issue,
I ran into this problem today and found that no matter what prefix or suffix I try, on every browser it emulates pressing F12 which opens the browser console.
The same barcode functioned as required a couple of weeks ago.
Every barcode comes with a quick start guide that you can use to set prefix suffix etc.
There is also a bar code that "Recalls Defaults". Just scan that and you should have the factory defaults set.
This resolved my issue.
Hope it helps someone.
For me the solution was to remove the "Line Feed" suffix ( which was not removed when I scanned the "remove all suffixes" code ), as the line feed is interpreted as CRTL-J on windows machines ... no idea why !?
( no time to research it either ;)
We have been using the following library for months:
https://unpkg.com/react#15.3.0/dist/react.min.js
Yes - I know we can just reference 15.3 and get the URL rewrite to the latest, but they released a breaking change. That's another issue for another day. Don't get distracted.
Yesterday this simply stopped working. You'll notice that if you load the URL mentioned, that the file is TRUNCATED. Simply cuts off. This made everything we use react with break. Interestingly, if you go to the following URL (without the .js extension) - things work.
https://unpkg.com/react#15.3.0/dist/react.min
My question is - what the heck happened? Why did the URL we've been using for 8 months suddenly stop working, and who can we get to fix it. In the interim, we had a copy locally that we've started referencing (which we probably should have been doing to begin with, since we don't want the automatic upgrade). When things like this happen, who do you inform?
I'm not sure you'll find the answer as to why this file is no longer working here but based off of the website you could reached out to the creator on twitter: https://twitter.com/mjackson
On the website it says:
SUPPORT
unpkg is a free, best-effort service and cannot provide any uptime or
support guarantees.
i.e. you should probably only use this link if you are messing around with a small project and shouldn't be used for any website where you actually care about the uptime of the site.
My hosted app is showing a floating banner with a notice saying “Installation of this item may not work properly.” on its Google Chrome Web Store product page. The app is undiscoverable by searching the Web Store.
What is causing this problem? I find no additional information in the developer dashboard.
If you get this message, it is probable that there really is an error in the manifest or locale files (For example, in my case it was a trailing comma on the locale files).
The process y follow to solve the problem was:
Try to instal the app version you have just submited to the chrome store. When you try to install the app you will probably get a error message thats points you on the track of the problem of your manifest file.
Solved the problem on the app and upload it again. You may get the same error on the developers panel. Two thinghs can be appening:
A) If you've already corrected all errors in the manifest files remenber to publish the changes and what is more important remenber that the publication process may take a few minutes to become effective. The message will disappear after a while if everything is okay. (This explains why is you look on the internet for that problem you find people saying that the message will disappear after a while)
B) If error persist event after the publishing process have been complete finished. You may have not solved all error on the manifest file go back to Step 1
cheers
I had this exact problem. When I tried installing, I got an error message about a missing file.
When I removed my locales directory, everything worked fine.
Chrome has this annoying prompt for reposting POST-forms.
While the idea of preventinmg double posts is nice, it doesn't make always sense since not every POST-form posts data in a forum or buys stuff in a webshop.
But Chrome has no option to disable this annoying behaviour.
Cannot "undo":
I have a POST-form where you can beautify text (sent via POST, returns beautified text). Sometimes it makes mistakes and you want to "undo" the submission so you go back in teh browser, but no! Chrome f***s you up with its annoying repost error message.
I cannot use GET since my form text is very long so i get the "URI too long" error.
How can this be fixed?
In the past the command line switch -disable-prompt-on-repost seemed to work, but that's no solution anyway since I cannot tell all my users to do this in order to use my website.
To my joy this morning, this appears to be removed (the popup when re-posting), I'm running version 29.0.1547.57. Not sure when it was removed.
However, I'm sure you redesigned your code/site long ago.
I have 5 users (3 locations) using the pages that have Tiny_MCE text areas.
I receive No Errors and it works Perfectly on the other 4 machines running IE7 This would indicate there is No JavaScript Errors.
One user only is seeing the raw html code and no buttons at all.
I suspect it must be some IE setting that is wrong.
It does not appear that Javascript is disabled, as other Javascript functions work on that same site on the same machine in IE.
This user is running XP Pro, and IE 7.
When I installed FireFox on his machine, the Tiny_MCE works perfectly. This would Also indicate there is No JavaScript Errors.
I'm at a loss to explain it.
Any Ideas would be appreciated.
Thanks
Once I ran into same issue and the fix was to remove a comma at the end of the script. So check whether the error pattern is present in your code.
For example, the following code contains a bug which will prevent it from running in IE7.
tinyMCE.init({
// General options
mode: "textareas",
theme: "advanced",
...
template_replace_values: {
username: "Some User",
staffid: "991234"
}, // <<< BUG - Additional comma here
});
If you can enable javascript debugging in IE7 then post the js error here.
Funny thing. The problem fixed itself with no human assistance. No Reboot, No Nothing. after being AFU for 2 weeks, it just started working again.
Got to Love Windows!
I've encountered this before and it has always been a caching issue. Use Ctrl-F5 in IE to force a full refresh of the page and all its files (*.css, *.js) in the browser and the browser cache. My guess is the IE 7 computer that was bad had a 14 day setting for checking if files were up to date.
Sometimes it's been worse - the web server (tomcat 5.5) would cache the file too and not notice the file was updated. Restarting the web server fixed that.
We are experiencing the same problem with our software last few months.
I found this forum topic on developer's website:
http://tinymce.moxiecode.com/punbb/viewtopic.php?pid=66594
In short words, he is recommending to set strict_loading_mode to true when initializing tinymce. I've done that, and since that i had no problems.