I just upgraded my iPhone 8 to IOS 13. When running the QuickBooks App on my iphone if i go to Expenses and try and create a new Expense, when i click 'SAVE' i get this error.
I uninstalled and reinstalled the Quickbooks App with no change. The IOS Quickbooks App appears to not work yet with IOS 13.
Hi there, mjbcomp.
There's currently an on-going investigation with this issue. Our engineers are working on getting it fixed.
For now, we recommend using a web browser when accessing QuickBooks Online.
We've got you some Community articles handy. You may review them if you have some time.
If you have any questions, please let us now. We are here to help.
I'm having the same problem and I 95% of my daily use is for entering expenses. More attention needs to be placed on this error.
Thanks for reaching out to the Community, ChuckC.
Our Engineering Team is working diligently to find a resolution. In the meantime, we’re asking for your patience and understanding while we’re continuing to fix on this. We’ll keep you posted on this thread as soon as an update is received.
We are actively searching for a permanent solution and we should see a fix soon.
As shared by my colleague GarlynGay above, you can create transactions using the mobile browser.
We continuously monitor the issue in the QuickBooks Online mobile app real-time. To help you get updated about the status, please visit this website: http://status.quickbooks.intuit.com/.
Thanks for your patience and please let me know if you have any questions. I'm here to help. Take care.
I see that there is an update for the IOS App Version 19.9.3.
It would be nice to know exactly what this fixed other than "Bug fixes and performance improvements."
I want to know if i can upgrade to IOS 13 and have my issue resolved.
What SPECIFICALLY does 19.9.3 FIX?
Our engineers are still finding the root cause of this issue, mjbcomp.
Rest assured, once we heard a permanent fix from them, either my colleague or I will post to this thread.
In the meantime, you can follow the workaround shared by my colleagues above.
I'd also suggest to reaching out to our Phone Support so your name will be added to the list of those affected users. Here's how:
I appreciate your patience while we're working to resolve this issue.
There has been 2 iOS updates from QuickBooks in the past 5 days. Have either update resolved my issue?
Thank you for getting back to us, @mjbcomp.
As of the moment, this on-going issue is still open and we're unable to give a specific timeframe as to when this will be resolved.
Know that our engineers are diligently working to fix this as soon as possible. Also, once you've been added to the list of affected users, you'll receive all available updates about this through your email.
In the meantime, you can consider following the workarounds discussed in this thread. You can pull up and access your account via a mobile browser and create your expense transaction from there.
Lastly, I've added this helpful article that'll help you handle your future tasks: QuickBooks Online Mobile App FAQs.
We appreciate your patience as we're working on this. Please let me know in the comment section down below if you have any other concerns.
I don’t know why this issue as marked as “SOLVED”. It is not solved and I visit here daily hoping to find a resolution. Asking me to use a browser to log in online is not an answer and unrealistic. For now I will simply not update to IOS 13.
i find it incredibly ridiculous that something as simple and routine as adding an expense in QB online in the iOS App wouldn’t have been vetted in QA. it’s not like this is an obscure task.
For now, we're still unable to save them due to the issue. Our engineers are working with IOS support team to make sure this will work.
Even if your old iOS version is working, I'd still suggest following the workarounds in this thread.
We'll give you updates once we receive any from our engineers. I'd appreciate your patience as they get to the bottom of this.
It's still being fix, mjbcomp.
For now, the best workaround that I can suggest is to use your mobile browser. From there, you can create and save an Expense transaction.
We'll keep this thread updated once this issue will be resolve. Thank you so much for your patience, mjbcomp.
The investigation status is still in progress, mjbcomp.
We're working with our engineers to gather more information on what's causing this issue. We want this fixed for you.
As of the moment, it would be best to use a mobile browser in accessing your account to create and save your expense transactions.
Your patience is much appreciated as we're looking for a permanent fix.
I have to agree with Mjbcomp, this is extremely frustrating. The main reason I use Quickbooks online is to be able to have quick access onsite and input expense. While the mothly cost for Quickbooks has continued to rise it's odd that the features are being reduced.
I understand the urgency of fixing this error. While our engineers are diligently working for a fix, rest assured that this will be a permanent fix.
Once we heard an update to our engineers regarding this issue, I'll make an update to this thread.
In the meantime, you can create transactions using the mobile browser as a workaround.
Also, to ensure you'll get an update about the resolution status, I recommend reaching out to our Technical Support Team. They have to collect personal data to add your company to the list of affected users and provide this number for easy tracking: INV-34990.
I appreciate your patience as we work for a fix. Please know that you can always get back to this post if you have any other questions.
So this issue has been open over a month now. Today another IOS update for Quickbooks was released Version 19.10.1. Did THIS update fix the issue?
This is not an obscure issue. Not being able to save an Expense charge is a very basic feature of the software. I'm still baffled why this issue isn't fixed.
The recent iOS update doesn't guarantee a complete fix of the issue. Currently, our engineers are still gathering information and working on resolving this.
You can follow the steps provided by my colleague @Mark_R as a workaround.
I've also added our page about apps for future reference.
Please know that we're always here if you need help with anything else.
This problem is resolved. I upgraded to IOS 13 and the problem doesn't exist anymore. So ONE of the 4 or 5 updates that have been rolled out since i reported the issue 6 weeks ago has solved it.