The app let me do a single lesson and then switched back to saying Cy/Welsh is unsupported.
Anyone need else have this happen?
The same thing happened to me with Ukrainian back when it wasn't supported by mobile. I was in a No Service area, and the Wi-Fi was poor, and I finished about 3 lessons of Ukrainian. Then, I went to an area with good service, and it stopped my lesson and said Ukrainian was unsupported. Then it erased the 3 lessons of progress that I did.
Courses that are in beta are not available on the app; when a course graduates out of beta, it's added to the app :) Hopefully this won't be long.
But in the meantime, use your device's native browser and go to the "full" website - it works exactly like the app :)
Hope you're enjoying the course.
The website hasn't worked on iOS for quite a while. It's rather annoying.
It works for me though not perfectly. Their buttons aren't optimised for mobile; have to tap things twice more often than not.
Same here. Also, I find I usually have to manually start the audio playing, but sometimes, apparently randomly, it plays automatically. The audio for individual words also only works once. It is necessary to tap another word, or play the whole sentence, on order to be able to get it to play again. Quite annoying/tedious when try hard to pick out a work!
The font is too small on the website (on an iPad), so some combinations of letters/accents are hard to make out clearly. It was a while before I realised it was 'plîs' not 'plis'!
I know it is possible to zoom-in with Safari, but it still makes it fiddly. I also prefer to use in portrait orientation - I suppose I could use landscape but that feels less comfortable and the keyboard becomes too big.
I much prefer the app, but Welsh isn't available (yet), of course. When it is, it won't have access to the notes or discussions, which with Welsh is proving fairly crucial.
That's odd. It's working on my iPhone 6. Maybe delete your cache from Settings > Safari?
I wondered if you might be on an older version. That probably rules that out as an issue. I'm still on 9.2. I've held back from 9.2.1 (the latest retail release) until all the new bugs have been found and I'm sure nothing I consider critical has been broken! :-)
The update could have caused you issues, but it was only released recently and you say it hasn't worked for quite a while, so it can't be that. Unless you are a developer and actually have a beta version 9.2.2 installed.
Are you using the default browser, Safari? Have you tried Chrome to see if that might work? Of if you are using Chrome, have you tried Safari?
[Hit lowest level - no reply button]
In what way doesn't it work? Are you able to start but the buttons don't work?
I know it doesn't help but it works OK for me on an iPad Air 2 running iOS 9.2. Do you have an older model iPad (can't be very old if it supports 9.2.1)?
Starting any lesson causes the browser to crash as it tries to load it. The rest of the website works normally.
It's an iPad mini which isn't the newest but this is the only time any feature on a website has caused both browsers to crash.
[no reply button]
Re: iPad mini... Hmm... That's weird.
It sounds perhaps as though the website might be making certain assumptions about the dimensions of the device and exceding some boundary condition. Frankly, if they are doing that it is bad design/coding practice. Either that or they're applying the wrong styles (CSS) but the code is expecting something else.
If you haven't already done so you should report it directly to Duolingo as a 'fatal' bug. They will need to know that it is an iPad mini running iOS 9.2.1 and that it is reproducible with both Safari and Chrome.
I suspect they may be expecting an iPhone and running the iPhone/mobile version of the site. I've noticed on iPad proper it runs the desktop version but for iPhone it runs a mobile version.
One thing you might try is viewing the page in desktop mode. For iOS 9.2/9.2.1 tap-and-hold the refresh icon to the right of the address bar in Safari and choose 'Request Desktop Site' before entering the lesson (i.e. after loading the Duolingo lesson tree) and see if that helps.? Sadly, it may not make any difference if they check on entry to each lesson and the force mobile version, which it sounds is what may be happening.
The desktop version of Duolingo doesn't play well with a full-sized iPad, requiring double-taps for buttons to work, badly sized pages and fonts etc, but it does work. So for a mini it might be more challenging, even if it works.
It may not Duolingo's fault. Apple introduced some bizarre bugs into Safari with iOS 9/9.2! For example the mega-sized font for Google's 'translate this page' - which is only available in the desktop version of results.
I have never had the option of using the mobile site, it's always been the desktop site for me. I think the mobile site may be an A/B test, it used to be, but perhaps it is now on all iPhones. Your theory about boundary constrictions is interesting, sometimes the blue banner at the top of the page manages to load before the page crashes on Safari but on Chrome it goes to the "owch" page immediately. I reported the problem to Duolingo but I should probably add some of these details to it.
Update: Out of curiosity I just tried requesting the desktop version on my iPhone. It didn't work! That is it did work but Duolingo ignores it and forces the mobile version.
So that may still work with an iPad mini, but it looks unlikely - sorry.
Since you say you get the desktop site, it suggests to me that different sections of the code are making different assumptions about what kind of device you are using and ending up in a mess.
So the browser apps aren't actually crashing, they are just going to 'ouch' pages? That could mean it is looking for code/style pages with encoded urls for specific devices, perhaps, but there isn't one that matches. Although in reality there are hundreds of ways of messing this sort of thing up and creating a similar result! So it could be almost anything! :-)
I thought Safari completely crashed but it seems to do the same as Chrome now after trying to load a few times. It's would be a shame if Duolingo doesn't try to fix it as I can no longer use Duolingo properly :/
You could also try the 'Opera mini' browser. If you tap the 'O' icon to the top-right it brings up settings. Tap 'user-agent' and choose 'desktop'.
However; sadly, I doubt it will work. It appears Duolingo may be ignoring this and coding for specific devices/operating system versions rather than capabilities. This is bad practice. It leads to exactly the type of issue you are experiencing and is a maintenance nightmare!
The true desktop (PC) version of Opera allows one to report/pretend it is various types and versions of browser. Useful for developers when testing compatibility of website client-side code and layout. Hint, hint Duolingo! :-)
Yes, it must be very frustrating. Hopefully, it is likely to be something easy to fix, once they find it. Unfortunately, because of they way (I suspect) they are doing it, I don't see any work-around. :-(
Usually courses are added to the app while they're still in Beta. Polish was quietly added to the app only a couple days after it had reached phase 2. I'm really not sure anymore what qualifies it for the app. In the past it seemed to be a couple of weeks or more after Phase 2 began after we had plenty of testing on the website, but after Polish, I'm not really sure anymore.
Yeah I usually get a message saying its not supported yet. However when I did my Welsh on the website and switched to the app for my German, Welsh was suddenly available! On long enough to for me to do one lesson then be told it's not supported. Must have just been a strange glitch.
Russian and Ukrainian are still in Beta, but they are available on the app as well... So I don't understand sometimes, who says a language could be in the app... :) Polish went out of Beta, I mean: forward, quite fast...
My understanding is that it is a matter of the percentage of problems being reported. Once it settles below a certain level it becomes considered for inclusion in the app. It appears that an update is then necessary, it doesn't automatically appear. Russian, I think appeared in the (iOS) app about 6 weeks after release in beta. I'm not sure if there is any defference between iOS and Android.
Sadly, if this is indeed how it is determined, it may take some considerable time for Welsh to appear in app. With the best will in the world, the Welsh course has a number of issues that need sorting. Without direct access to the notes or discussions in the (iOS anyway) app, the Welsh course will prove pretty challenging to anyone attempting it entirely via the app,
It's always told me the course isn't available in the app but it does work perfectly well through a mobile browser. That said, I tend to only do timed practice on a computer rather than smartphone, as the shortcuts are much more efficient when using a real keyboard.
If you have Apple stuff, update Duolingo, Welsh is available now also in the app :)