Amcrest View Pro (iOS v3.40.0057) - Login Timed Out

[grabczb]

Narrowfoot - I'm using iOS IP Cam Viewer. The free version works great but just doesn't have a mic/speaker option. Other than that, they have Amcrest models listed in the setup. Hopefully that helps you gets up and running until Amcrest fixes their app.

Good luck!

Bernie

[grabczb]

Also adding 100% support to narrowfoot's post. Your app updates continue to be untested before release to the public. This is not an mature product at all and does impact the reputation of your company. You really need to require "change management procedures" with your app developers. The return of a month old login timeout issue Is NOT acceptable.

[tph018nwu]

Hi Raheel,

Yes, this time out issue affects all ports. I am using the IP/Domain setup on the app to connect to the camera on the mobile device. I have multiple IP cameras, each on the same DNS (yes, a DNS service like no-ip) but with a different port for each camera. I am unable to connect with any of the cameras via the app based on the changes implemented in the Feb 16 app update. This is the same issue as was experienced about 3 weeks back in which a new rollout of the app caused the IP/Domain setup to no longer work before Amcrest reverted back to an older version that did work.

Note, I am able to connect to the external IP address of each camera using a browser from my mobile device or from a computer.

I am also able to successfully connect to the cameras on the app using the Serial Number (S/N) (P2P) but would much rather use IP/Domain to connect on the app.

Please resolve this ASAP!

[nyJules]

As of Feb 16, the problem with Login Timeout that occurs with the IOS app Amcrest View Pro and first appeared with iOS v3.40.0057 of the app has REAPPEARED when iOS v3.40.0060 was pushed to IOS devices.

This is crazy! It's unacceptable. Eventually, after a few weeks, the problem with v3.40.0057 was resolved by another version.

But now, only a month later, Amcrest pushes v3.40.0060 to all IOS devices, and the View Pro app is BROKEN again.

C'mon Amcrest. Once you have a stable version of the app that is working, stop screwing around with it by pushing new, untested versions to your customers. We are NOT your Quality Assurance department.

If the View Pro app is unusable, we don't need your cameras. We'll go somewhere else to buy cameras and WORKING apps.

Please fix this problem.

Jules

[narrowfoot]

well said Jules

[Raheel]

Hey everyone,

Giving a quick update, after working with a few users with this problem it seems that the issue is related to users who are utilizing HTTP ports as the port inside the mobile app when connecting to a camera using the IP/Domain method.

If you are having this issue, please try forwarding a TCP port in your router and setting that port as your TCP port in the camera via the web interface. Once you've done this, edit the camera details in your mobile app and set the port to the TCP port. This should work as I have verified that a few end users were able to resolve the problem.

Originally, the update we had pushed out 2 versions ago was intended to fix a landscape issue bug as well as add on additional P2P enhancements for the app. Due to receiving a lot of feedback regarding customers cameras not working anymore, we made the decision to roll back the app entirely as we assumed this problem was related to P2P connectivity, without delving into it further due to having customers who would not be able to connect to their camera. After doing this, we wanted to at least push out an update that fixed the landscape view issue only, leaving the P2P code completely untouched, which we assumed was the root cause of this issue.

After this latest update, we've finally seen that it seems to be related to HTTP ports not working in conjunction with an IP address, and not related to P2P at all. That being said again, if you try utilizing the TCP port instead, this should get you connected to your camera. We also only received a handful of users who were experiencing this issue, which seemed to make it a very isolated, specific case that we wanted to ensure we could reproduce.

If anyone can report that utilizing the TCP port (that is port forwarded) in conjunction with your IP or DDNS does NOT work, please let me know or send an email to [email protected] so we can investigate this immediately.

[narrowfoot]

Raheel, you are asking users to modify their network, when the PROBLEM IS WITH YOUR APP. I say this based on the fact the camera is perfectly accessible and usable with the browser-based Amcrest Viewer and with third party iOS apps.

Why don't you fix the root cause of the problem?

[Raheel]

Raheel, you are asking users to modify their network, when the PROBLEM IS WITH YOUR APP. I say this based on the fact the camera is perfectly accessible and usable with the browser-based Amcrest Viewer and with third party iOS apps.

Why don't you fix the root cause of the problem?

Hey narrowfoot,

A new app was released last night for internal testing and will be uploaded to the App Store today, usually Apple takes a few days to post newly published apps after their review process so the updated version should be live by end of the week if the review process proceeds without issues. My last message was moreso a recommendation for users who needed to get their cameras working on their mobile app temporarily while we fixed the issue, as well as a brief background of the situation and an alternative resolution to the problem at hand. Connecting to the serial number of the camera using the app or opening a TCP port will both work without issues, which is what I wanted to specify as an alternative.

[narrowfoot]

still waiting... what is the ETA?

[nyJules]

Me too... Still waiting for something to replace v.3.40.0060 which BROKE the View Pro app AGAIN.

But if (and when) the problem is fixed, I'm changing the settings in my iPhone so that apps will NOT automatically update. I'll look for updates myself... if I choose to do so.

Jules