you might be waiting a while… it’s been over month (maybe two?) since it was submitted to Apple. No word from the dev in weeks… I know he’s got ‘life issues’ at the moment, but I think all of this adds up to 2.0 isn’t happening anytime soon.
Can somebody confirm the issue Jim is having with 0.100.0b0?
People in my slack group have the same problems. But haven’t seen them on the forums yet though.
It’s not just Jim. There’s a bunch of people on discord with same problem including me.
UPDATE: it’s working again in beta 0.100.0b1
Oops… just started crashing again
Hey ! I was wondering if it would be possible to have lovelace on Apple watch ? I mean … i could do a view specific for my watch and put custom tiny button !
@DavidFW1960 did you happen to try it on 0.100.0b2? Just out of curiosity.
I want to update, but obviously not if the app isn’t working (especially my wife didn’t like it that the app didn’t work for some time 
)
Anyways I am really curious if you have tried this already.
Balloob says it’s an ios app fix needed and it doesn’t work on b2 or b3 either
Ah ok that seems to clarify things. Well at least I don’t need to try anymore . I don’t want to bother Robbie with the app, but knowing that you know a lot of this stuff I might as well ask, is the app still being developed? Just out of curiosity again.
I know he had some family matters so I don’t want anyone to feel pressured or anything. I rely on this app so that is why I ask but at the same time I like to be up to date. Is the app going to get the fixes it need anytime soon or not? No hurries though, I can do fine with the current version, I am just curious that’s all.
Thanks for the clarification.
On discord, Robbie said he’s hoping to have a fix out today for the iOS app for 0.100.0
Of course it’s still being developed. He has submitted 2.0 a few times for approval but the heat was off once he pushed a new beta a few weeks ago… no point rushing something out just cos…
No problem, that clarifies it for me 
. I wish I knew how to code I so I could be of any help to all of you.
Anyways thanks for informing me (and us).
Edit: btw, do you know why the app isn’t approved yet by Apple? I mean the type of app and what it can do isn’t that much different from the previous one. Ofc it is completely different in all other areas but still.
Speculation only: First I believe it’s now not going to be released as an upgrade but as a whole new app. Second, you will be able to donate via the app and I think that triggers some issues in the approval process. Lastly, Robbie has been busy with life stuff and the app first stalled in the approval process - once for 3 wees when iOS13 came out and Robbie withdrew it and resubmitted. I think it may have been rejected once or twice as well.
Because the beta has 3 months to run, it’s also not urgent and probably isn’t getting the attention it needs to ram it through. Robbie was originally hoping to not have to extend the beta but had to because the release was held up. So this gives opportunity to squash other bugs before release as well.
As I said it’s all my speculation and what I have gleaned by hanging around the #ios channel on discord.
1 Like
Fix for HA 0.100.0 has been released…
crashes…
1 Like
Looks like build 64 has been pulled. It was crashing instantly for me as well.
Crashing here too immidately when I try to start…
Me too and I am on 0.99.3 couldn’t downgrade iOS app so uninstalled and now because the crashing build is removed I can’t reinstall either.
Never mind found the previous build in test flight and got it installed.
100.0 crashed, 100.1 works fine for me (build 63, 8Plus iOS 13.1.2)
That’s odd. All I see in 100.1 is a withings change. Hmmmm
Can I update now to 0.100.1 and use the iOS 2.0 App or do I have to wait for an iOS app update?
For me it started crashing only around 12 hours after I did the update (really strange btw). Though notifications and device tracking still worked even with the crashing app. From what I have heard it is a problem within the app and needs a fix. I doubt it that 100.1 has fixed the problem. Could you try clearing the cache, hard-close the app and retry?