@shireeshabongarala which fix?
@dkayiwa fix with this commit https://github.com/openmrs/openmrs-module-appointmentscheduling/commit/86936c058f2f789ccf468a62039807b756df4f06.
We were able to fix the issue with building the omod locally (which has the fix). So, we are waiting for new release of appointment scheduling with the fix @shireeshabongarala pointed out. Any idea when would that happen ?
The module release can happen any time you want. @sravanthi17 being a /dev/3 you should be able to release. 
You could release from bamboo: https://ci.openmrs.org/browse/AS-ASML/latest as instructed here: https://wiki.openmrs.org/display/docs/Releasing+a+Module+from+Bamboo
Or use this: https://wiki.openmrs.org/display/docs/Maven+Release+Process
@dkayiwa once this release has happened I think that someone with access to the core infrastructure (like you) should ensure that the demo server gets updated.
I would suggest doing a 2.5.1 maintenance release of the Reference Application distro which is exactly like 2.5 but just includes this new version of appointment scheduling. And updating demo to run this.
(I am not proposing refapp maintenance releases for minor bugfixes in general, but only in the specific case where top-level features are unusable. I.e. this case, and also the one where you can’t capture environmental allergies.)
@sravanthi17 I had tried to install it and when I chose a patient from the manage appointments section, I got an alert message asking me to login although I was already logged in. One of my friends also tried installing it and got the same error. Were you able to completely use the appointment scheduling module without getting this error?
Yes, we were able to use the module (with out appointmentSchedulingUi). We got the latest of all the required modules built locally.
@sravanthi17 Thanks for the info! I think we get the error that I got when we use the appointment scheduling UI .So basically it has something got to with the UI .