search

ahmedchoteri / openintents

Automatically exported from code.google.com/p/openintents
0 stars 0 forks source link

OI Safe- Toasts are display even when user exists from application #516

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Open OI Safe
2.Enter no/wrong password
3.click on "Continue" button very fast a lot of times
4.Exit from application

What is the expected output? 
Toasts are scheduled for each click on Continue button, which continues to 
display even when user exits form application.

What do you see instead?
Toasts should not display when user exits from OI Safe application.

What version of the product are you using? On what operating system?
OI Safe 1.3
Android version 2.3.6(Gingerbread)

Original issue reported on code.google.com by kumarsuk...@gmail.com on 29 Mar 2012 at 4:07

GoogleCodeExporter commented 8 years ago 
*correction:

What steps will reproduce the problem?
1.Open OI Safe
2.Enter no/wrong password
3.click on "Continue" button very fast a lot of times
4.Exit from application

What do you see?
Toasts are scheduled for each click on Continue button, which continues to 
display even when user exits form application.

What is the expected output? 
Toasts should not display when user exits from OI Safe application.

What version of the product are you using? On what operating system?
OI Safe 1.3
Android version 2.3.6(Gingerbread)

Original comment by kumarsuk...@gmail.com on 29 Mar 2012 at 4:11

GoogleCodeExporter commented 8 years ago 
Solution posted...

https://groups.google.com/forum/?fromgroups&hl=en#!topic/openintents/0kwiig3oKf4

Original comment by rmce...@gmail.com on 20 Jun 2012 at 12:29

GoogleCodeExporter commented 8 years ago 
Committed 
https://github.com/openintents/safe/commit/9e2ff4daf5276e1a356c5512bc08298d29c8a
8db

Original comment by friedger@gmail.com on 4 Jul 2012 at 7:25

GoogleCodeExporter commented 8 years ago

Original comment by friedger@gmail.com on 4 Jul 2012 at 8:00

GoogleCodeExporter commented 8 years ago 
Should the status of this issue be changed to fixed or did I mess up something 
with the patch?

Original comment by VenGeanC...@gmail.com on 24 Aug 2012 at 9:26